(Illustration by Gaich Muramatsu)
On Wed, 23 Jun 2004 16:34:10 -0700, Steve Simitzis wrote: > you could just type "where" after starting up gdb to see where it > crashed. i'm not too much of a pro with gdb, but "where" usually > gives me enough information. Crash during bonnie testing: venus.err: 15:03:00 Fatal Signal (11); pid 876 becoming a zombie... 15:03:00 You may use gdb to attach to 876 gdb where #0 0x401822a6 in sigsuspend () from /lib/tls/libc.so.6 #1 0x080c8738 in SigChoke (sig=357693596) at sighand.cc:241 #2 <signal handler called> #3 0x0807509e in fsobj::Open (this=0x75b67a48, writep=0, execp=0, truncp=0, cp=0x15521e18, uid=0) at fso.h:686 #4 0x080c1018 in vproc::open (this=0x817eea0, cp=0x15521e18, flags=1974893128) at vproc_vfscalls.cc:223 #5 0x080c6f03 in worker::main (this=0x817eea0) at worker.cc:1327 #6 0x080bb516 in VprocPreamble (init_lock=0x0) at vproc.cc:146 #7 0x4005b476 in Create_Process_Part2 () at lwp.c:796 #8 0x4005c303 in L1 () at process.S:455 -- Gabriel WickeReceived on 2004-06-25 09:12:06