Article View: gnu.gdb.bug
Article #10129elided info in backtrace
From: Stephen Gildea
Date: Mon, 04 Jun 1990 15:14
Date: Mon, 04 Jun 1990 15:14
15 lines
1254 bytes
1254 bytes
In GDB 3.5 (and earlier 3.x versions), gdb saves time at startup by not reading in all the symbol data. The first time you access a symbol in a new source file, you get the message, "Reading in symbols for ...." The problem comes when looking at a backtrace. For each of the frames in files we have not read in symbols for, "..." is displayed for the argument and line number information. Stepping through all the frames by typing "up" repeatedly reads in the information, and another "bt" will then print it all. I would like there to be a single command that will read in all the symbols necessary to show me all the information in a backtrace. < Stephen
Technical Details
Message-ID:
<9006041514.AA23292@life.ai.mit.edu>Path:
arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!tut.cis.ohio-state.edu!ALEXANDER.BBN.COM!gildeaShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f5053,16ed126fd4b316a6,start X-Google-Attributes: gidf5053,public X-Google-ArrivalTime: 1990-06-04 08:52:18 PST Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!tut.cis.ohio-state.edu!ALEXANDER.BBN.COM!gildea From: gildea@ALEXANDER.BBN.COM (Stephen Gildea) Newsgroups: gnu.gdb.bug Subject: elided info in backtrace Message-ID: <9006041514.AA23292@life.ai.mit.edu> Date: 4 Jun 90 15:14:03 GMT Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 15 Posted: Mon Jun 4 16:14:03 1990