From owner-freebsd-hackers Thu Mar 30 10:53:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id E433737BDBD for ; Thu, 30 Mar 2000 10:53:21 -0800 (PST) (envelope-from sam@inf.enst.fr) Received: by ada.eu.org (Postfix, from userid 1000) id 280EA19094; Thu, 30 Mar 2000 20:53:20 +0200 (CEST) To: freebsd-hackers@freebsd.org Subject: Remote GDB and call stack Date: 30 Mar 2000 20:53:19 +0200 Lines: 28 User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-03-30-20-53-20+trackit+sam@inf.enst.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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