windbg setting conditional breakpoint

僤鯓⒐⒋嵵緔 提交于 2019-12-01 23:03:57

you can not set a conditional breakpoint on a user32.dll since it's being mapped into the address space relatively early and the initial debugger's breakpoint triggers after that (as far as i know).

provided you can track the moment user32.dll is loaded, you can override a module break like this:

sxe ld user32.dll

what you could do is have your app get started by a boostrapper application and then have windows debugger break on user32.dll load. just use -o command-line option or .childdbg 1 extension call to initiate debugging of child processes and have it started with cmd.exe, for instance:

windbg -c "sxe ld user32.dll;g" -o cmd.exe /C yourapp.exe

I am a little confused by the text and header in your question. But assuming you want to set a conditional breakpoint you should take a look at the documentation cause it goes into plenty of detail on that subject.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!