Re: compile-goto-error but for gdb backtrace output

[Andreas Schwab]

eliz@is.elta.co.il (Eli Zaretskii) writes:

|> On 16 Apr 2001, Dan Jacobson wrote:
|> 
|> > Looking at a gdb backtrace, in buffer *gud-some_file* 
|> > 
|> > #7  0x8048e3d in read_tm (x_and_y_pair=0xbffff894, the_island=0xbffff870, 
|> >     one_line=0xbffff7ec "#comments have # at beginning\n") at funcs.c:225
|> > #8  0x8048597 in main () at tm2pole.c:41
|> > 
|> > one wonders if one could put the cursor on line "#7" and hit some key
|> > and be taken to that spot in that file, like in compile, grep, occur,
|> > etc. etc,. modes.  This would be a nice addition to debugger mode.
|> 
|> AFAICS, it already works that way if you invoke Speedbar.
|> 
|> In addition, typing "up 7" (to get to frame 7)

This will only work if you are currently at the innermost frame.  To
address the frame in an absolute manner, use "frame 7" (or just "f 7" for
short).

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5