remote kernel gdb stack frames corrupted after breakpoint or step

From: Kip McAtee <kmcatee_at_firetide.com>
Date: Wed, 15 Sep 2004 11:04:23 -1000
Greetings-

I'm building on 5.3-BETA4 (and 6.0 current)
with gdb (and kgdb) 6.1.1.

I can get into the remote kernel debugger with
sysctl debug.kdb.enter=1

I can set a breakpoint and continue.
When it hits the breakpoint I get:

Breakpoint 2, wakeup (ident=0xc0c0f9e8) at ../../../kern/kern_synch.c:253
253             sleepq_broadcast(ident, SLEEPQ_MSLEEP, -1);
(kgdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.

Looking at the backtrace implies that the stack frames
are not displayed correctly. I'm setting:

machine         i386
cpu             I486_CPU
cpu             I586_CPU

options         CPU_ELAN
options         CPU_GEODE

makeoptions     DEBUG=-g
options         KDB
options         DDB
options         GDB

All flavors of step, next, etc are failing, but I
can dereference variables in the current stack frame.

Thanks-
Kip
Received on Wed Sep 15 2004 - 19:04:26 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:12 UTC