Date: 30 Mar 2000 20:53:19 +0200 From: Samuel Tardieu <sam@inf.enst.fr> To: freebsd-hackers@freebsd.org Subject: Remote GDB and call stack Message-ID: <2000-03-30-20-53-20%2Btrackit%2Bsam@inf.enst.fr>
next in thread | raw e-mail | index | archive | help
I am investigating i386/17228 (Installation floppies hang up on Compaq
Armada V300 laptop) that I submitted.
I built a custom kernel with no SCSI at all (it had been suggested
that NCR probes could be the cause of the lockups) and with remote gdb
enabled.
I can enter remote gdb just fine using the keyboard interrupt, but the
call stack is pretty useless to me:
Program received signal SIGTRAP, Trace/breakpoint trap.
0xc02060ed in Debugger ()
(gdb) where
#0 0xc02060ed in Debugger ()
#1 0xc02030f2 in scgetc (sc=0xc027d520, flags=2)
at ../../dev/syscons/syscons.c:3134
#2 0xc0200169 in sckbdevent (thiskbd=0xc0276280, event=0, arg=0xc027d520)
at ../../dev/syscons/syscons.c:634
#3 0xc01f82e6 in atkbd_intr ()
#4 0xc021add4 in atkbd_isa_intr ()
Is there a way to know what was executing before the keyboard
interrupt and go there? I need to step in the code, because the freeze
is a real one, no keyboard interrupts will be generated anymore.
Sam
--
Samuel Tardieu -- sam@inf.enst.fr
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2000-03-30-20-53-20%2Btrackit%2Bsam>