From: Jeff D. <jd...@ka...> - 2000-10-05 15:30:57
|
Can you apply the patch below and do the stack overflow thing again? Do it like you did before except without the "handle SIGSEGV..". Also make sure that when it says "Attaching to program: /home/wstearns/uml/rh6.2/linux, Pid 1", the executable it names is the one that you're actually running. And make sure that it has symbols in it. This sort of suggests that it didn't: (gdb) b start_kernel No symbol table is loaded. Use the "file" command. I think one of these is what caused your problems last time. When you see things like: 0x10038fbd in ?? () it usually means that gdb is getting symbols from the wrong executable or it's not getting symbols at all. I think that also explains this stuff: warning: Couldn't get registers. warning: Couldn't get registers. warning: Couldn't get registers. #0 0x100a96dd in ?? () Error accessing memory address 0x5005332c: No such process. Jeff --- arch/um/kernel/trap_user.c~ Mon Sep 25 17:04:54 2000 +++ arch/um/kernel/trap_user.c Thu Oct 5 11:16:31 2000 @@ -208,6 +208,7 @@ } break; case SIGCONT: + case SIGSEGV: break; default: if(debugger_pid != -1){ |