Article View: gnu.gdb.bug
Article #45Re: problem with "where" command in gdb v3.1.2
From: Ron Guilmette
Date: Fri, 16 Jun 1989 20:15
Date: Fri, 16 Jun 1989 20:15
13 lines
1020 bytes
1020 bytes
I have often seen the problem described by Amante with GDB.
A simple solution is to set a breakpoint on the library
function named "abort" before you start executing the program
being debugged. Then, when you hit that breakpoint, the
"where" command should still work. By the time you make it
into abort (or kill) however, the "where" command does in
fact give you only incomplete information.
// Ron Guilmette - MCC - Experimental Systems Kit Project
// 3500 West Balcones Center Drive, Austin, TX 78759 - (512)338-3740
// ARPA: rfg@mcc.com
// UUCP: {rutgers,uunet,gatech,ames,pyramid}!cs.utexas.edu!pp!rfg
Technical Details
Message-ID:
<8906162015.AA03353@pink.aca.mcc.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!MCC.COM!rfgShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!MCC.COM!rfg From: rfg@MCC.COM (Ron Guilmette) Newsgroups: gnu.gdb.bug Subject: Re: problem with "where" command in gdb v3.1.2 Message-ID: <8906162015.AA03353@pink.aca.mcc.com> Date: 16 Jun 89 20:15:52 GMT Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 13