Hey,
(SEH -- I assume we're talking MS Windows)
A debugger attached is one solution (since a debugger is notified of
an exception before SEH is executed). PyDbg seems like a good idea,
but it can be done easily using the debugger API of Win32API too (just
forward all events except exceptions to
Hi list,
When i run some fuzzing tests i can't trap the exception when found some
bug due invalid input. I'm trying to figure out a smart way to handle
the exception, and tell me when it run.
On the PoC i've got the daemon crashed but it still working whithout
response the requests.
I'm reading
On 11/04/2010 06:30 AM, primehaxor wrote:
Hi list,
When i run some fuzzing tests i can't trap the exception when found some
bug due invalid input. I'm trying to figure out a smart way to handle
the exception, and tell me when it run.
Your question lacks specifics.
On the PoC i've got the
