This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: backtrace changes current source location
- From: Daniel Jacobowitz <drow at false dot org>
- To: Andrew Cagney <cagney at gnu dot org>
- Cc: Felix Lee <felix dot 1 at canids dot net>, gdb-patches at sources dot redhat dot com
- Date: Wed, 27 Oct 2004 13:40:07 -0400
- Subject: Re: backtrace changes current source location
- References: <20041026075115.4A2C354AAB5@stray.canids> <20041026132924.GA26886@nevyn.them.org> <20041026150127.6ED3E54AAB5@stray.canids> <417FDC11.7060700@gnu.org>
On Wed, Oct 27, 2004 at 01:34:09PM -0400, Andrew Cagney wrote:
> Felix Lee wrote:
> >patch for
> > http://sources.redhat.com/ml/gdb/2004-10/msg00414.html
> >
> >gdb/ChangeLog
> >2004-10-26 Felix Lee <felix+log1@specifixinc.com>
> >
> > * stack.c (backtrace_command_1): Backtrace shouldn't
> > change current source location.
>
> Felix, can you find out where current_sal is being trashed? GDB's
> trying to get away from all this global state - the code at that level
> shouldn't need to meddle with current_sal.
If you follow the link in his message above, Keith introduced it in
2002 - print_frame_info_base.
--
Daniel Jacobowitz