This is the mail archive of the gdb@sourceware.org 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: info on "value being assigned to is no longer active" error


On Fri, Jan 18, 2008 at 08:26:17PM -0800, Siva Velusamy wrote:
> Thanks. Should gdb be able to handle this correctly, or is this a
> situation where it is tough to define the correct course of action?
> 
> If gdb should handle this, what sort of change would be appropriate in
> the target specific code?

The problem is not a target-specific one.  I know I've discussed the
appropriate fix on the list at some point in the past two years; the
problem arises because we use null_frame_id as the ID of the outermost
real frame and to mark invalid frames.

The simplest fix might be to introduce another invalid frame ID and
use that for outermost frames.  A better fix would be to always use
valid frame IDs, and mark non-unwindable frames some other way.

-- 
Daniel Jacobowitz
CodeSourcery


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