sh1nu11bi / sulley

Automatically exported from code.google.com/p/sulley
GNU General Public License v2.0
0 stars 0 forks source link

process_monitor failing to handle access violation following a C++ exception #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
This issue has been moved -> https://github.com/OpenRCE/sulley/issues/2

Original comment by fitblip@gmail.com on 13 Apr 2012 at 8:35