From: Jeff D. <jd...@ka...> - 1999-12-21 21:07:31
|
> (gdb) backtrace #0 panic ( > fmt=0x1013eea0 "wait_for_stop failed to wait for %d to stop with > %d\n") > at panic.c:86 #1 0x1006e322 in wait_for_stop (pid=1865, sig=19) > at user_util.c:285 #2 0x100696a4 in start_fork_tramp > (saved_regs=0x50554228, > sig_stack=1349529600) at process.c:115 #3 0x1006ab11 in > do_proc_op (pid=1864) at process_kern.c:233 #4 0x1006d4a2 in signals > (arg=0xbffff5e8) at trap_user.c:119 Good. I just fixed that bug. Ironically, that's in the code that fiddles with the command line, so that when you do ps from outside, you get to see what each thread is doing. It is purely aesthetic code, and it reduced the kernel's reliability. Jeff |