Displaying 2 results from an estimated 2 matches for "do_segv".
Did you mean:
do_recv
2001 Dec 11
1
VirtualProtect and app crash: exception handling?
...SetErrorMode says so.
So what's with this trace?
0806d398:trace:seh:EXC_CallHandler calling handler at 0x761b10
code=c0000005 flags=0
It looks like we're calling 0x761B10, not 0x75F447. Why?
It also looks like EXC_CallHandler is called from EXC_RtlRaiseException,
which is called from do_segv, which is called from a signal handler for
SIGSEGV.
Why does do_segv call EXC_RtlRaiseException, and not
UnhandledExceptionFilter? Where did EXC_CallHandler get that 0x761B10
address from?
--Rob
2001 Dec 08
1
LoadOEMResource crash [Was: Re: Problem report: SHRINKER.ERR, fix to DEVICE_Open/CreateFileA? ]
...t 3, EXC_RtlRaiseException (rec=0x404f3c60, context=0x404f3cdc)
at exception.c:176
176 TRACE( "code=%lx flags=%lx\n", rec->ExceptionCode,
rec->ExceptionFlags );
(gdb) where
#0 EXC_RtlRaiseException (rec=0x404f3c60, context=0x404f3cdc) at
exception.c:176
#1 0x40076748 in do_segv (context=0x404f3cdc, trap_code=14,
cr2=0x45f00c, err_code=4)
at signal_i386.c:711
#2 0x40076ada in segv_handler (__signal=11, __context=
{sc_gs = 0, __gsh = 0, sc_fs = 143, __fsh = 0, sc_es = 43, __esh
= 0, sc_ds = 43, __dsh = 0, sc_edi = 4583440, sc_esi = 4583424, sc_ebp =
10789357...