This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RFA symtab: Fix for PR c++/1267 ("next" and shared libraries)

From: Andrew Cagney <ac131313 at redhat dot com>
To: Daniel Jacobowitz <drow at mvista dot com>
Cc: gdb-patches at sources dot redhat dot com, ezannoni at redhat dot com,jimb at redhat dot com, fedor at doc dot com
Date: Mon, 21 Jul 2003 14:22:34 -0400
Subject: Re: RFA symtab: Fix for PR c++/1267 ("next" and shared libraries)
References: <20030719181817.GA11670@nevyn.them.org> <3F1C1254.2070007@redhat.com> <20030721162750.GA6754@nevyn.them.org>


No, really, I still think that the comment is wrong.  The get_frame_id
call triggers the prologue analyzer to analyze the NEXT frame.  I.E.
this_id is called with the NEXT frame, and THIS cache.

Nope. get_frame_id triggers the analysis of THIS frame's prologue (i.e., next_frame & this_cache).

The call to frame_pc_unwind uses THIS frame and creates the PREV cache. It's one frame off on the stack. The frame it would be saving from prologue analysis is not the one we'd need to analyze for the get_frame_id call.

Nope. frame_pc_unwind would turn into frame_register_unwind (this, PC_REGNUM) and that will also trigger the analysis of THIS frame's prologue (i.e., next_frame & this_cache).

Andrew

Follow-Ups:
- Re: RFA symtab: Fix for PR c++/1267 ("next" and shared libraries)
  - From: Daniel Jacobowitz

References:
- RFA symtab: Fix for PR c++/1267 ("next" and shared libraries)
  - From: Daniel Jacobowitz
- Re: RFA symtab: Fix for PR c++/1267 ("next" and shared libraries)
  - From: Andrew Cagney
- Re: RFA symtab: Fix for PR c++/1267 ("next" and shared libraries)
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]