Running some apps leave me sometime having an exception in the debugger, so gdb is called. And many times the function that appears when gdb is called is nanosleep(). Should I consider this as a libc issue ?
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Running some apps leave me sometime having an exception in the debugger, so gdb is called. And many times the function that appears when gdb is called is nanosleep(). Should I consider this as a libc issue ?
two questions: - what's the type of the exception ? - is the address of the exception really at nanosleep (and not something like nanosleep + 0x????zillion ?)
A+
--- Eric Pouech eric.pouech@wanadoo.fr a écrit : >
Running some apps leave me sometime having an
exception in the debugger, so gdb is called. And many times the function that appears when gdb
is
called is nanosleep(). Should I consider this as a libc issue ?
two questions:
- what's the type of the exception ?
wine_dbg: Exception (c0000005) inside debugger, continuing... Always the same.
- is the address of the exception really at
nanosleep (and not something like nanosleep + 0x????zillion ?)
Backtrace from gdb :
#0 0x420b4b31 in nanosleep () from /lib/i686/libc.so.6 #1 0x420b4a6b in sleep () from /lib/i686/libc.so.6 #2 0x4037081a in DEBUG_ExternalDebugger () at ext_debugger.c:153 #3 0x4037d756 in wine_dbg (__eptr=0x403b48dc) at winedbg.c:138 #4 0x400cca11 in __wine_exception_handler (record=0x403b49c8, frame=0x404c6c28, context=0x403b4a44, pdispatcher=0x403b4958) at exception.c:375 #5 0x400cc39f in EXC_CallHandler (record=0x403b49c8, frame=0x404c6c28, context=0x403b4a44, dispatcher=0x403b4958, handler=0x4038c628 <__wine_exception_handler>, nested_handler=0x400cc2d8 <EXC_RaiseHandler>) at exception.c:117 #6 0x400cc69c in EXC_RtlRaiseException (rec=0x403b49c8, context=0x403b4a44) at exception.c:213 #7 0x400d47c7 in do_segv (context=0x403b4a44, trap_code=14, cr2=0x80bad34, err_code=4) at signal_i386.c:747 #8 0x400d4c56 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 = 0, sc_esi = 134911800, sc_ebp = 1078749588, sc_esp = 1078748636, sc_ebx = 1077478776, sc_edx = 17791, sc_ecx = 134914544, sc_eax = 1089077248, sc_trapno = 14, sc_err = 4, sc_eip = 1077364875, sc_cs = 35, __csh = 0, sc_eflags = 66054, esp_at_signal = 1078748636, sc_ss = 43, __ssh = 0, i387 = 0, oldmask = 0, cr2 = 134982964}) at signal_i386.c:923 #9 <signal handler called>
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Sylvain Petreolle a écrit :
Running some apps leave me sometime having an exception in the debugger, so gdb is called. And many times the function that appears when gdb is called is nanosleep(). Should I consider this as a libc issue ?
not at all. gdb is launched because of an exception inside the debugger to ensure that gdb is started, winedbg waits, in the fault handler for some time, to let gdb attach to the winedbg process that's why you see the nanosleep at the top of backtrace the interesting part is to know where the debugger crashed (ie the PC, and the function from the exception frame at the bottom of the backtrace)
A+
not at all. gdb is launched because of an exception inside the debugger to ensure that gdb is started, winedbg waits, in the fault handler for some time, to let gdb attach to the winedbg process that's why you see the nanosleep at the top of backtrace the interesting part is to know where the debugger crashed (ie the PC, and the function from the exception frame at the bottom of the backtrace)
A+
Ok, but this will wait :( I encounter the "parse error problem" today : (without any changes to the source/to my system)
Wine-dbg>parse error Cannot pass on last chance exception. You must use cont
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
-
Eric Pouech -
Sylvain Petreolle