[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Eli Zaretskii
Subject: Re: compile-goto-error but for gdb backtrace output
Date: Mon, 16 Apr 2001 15:26:04 +0300

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) should automatically 
display the source line of frame #7, even without Speedbar.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]