From Matt Watchinski:
"For the life of me I can't get process_monitor to generate a crashbin
or log test cases that caused a crash, even though the applications
blows up.
Seems the applications throws exception code e06d7363, process_monitor
sees "first chance", then it skips it. The app then NULL ptr
dereferences and dies. Under WinDbg this causes a second chance
exception and everything works as expected. PyDBg just says "thread
exiting" and then Sulley restarts the app and moves on to the next fuzz
case.
When I added something other than None to the _log lamda on pydbg I can
see pydbg sees the C++ exceptions, says it's unhandled, says it's first
chance and then pydbg bails the thread."
Original issue reported on code.google.com by aport...@gmail.com on 6 Dec 2007 at 5:54
Original issue reported on code.google.com by
aport...@gmail.com
on 6 Dec 2007 at 5:54