From: Daniel Jacobowitz <drow@false.org>
To: Siva Velusamy <siva.velusamy@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: info on "value being assigned to is no longer active" error
Date: Sat, 19 Jan 2008 04:43:00 -0000 [thread overview]
Message-ID: <20080119044333.GA29595@caradoc.them.org> (raw)
In-Reply-To: <e7dfeff00801182026h52b7fe6eo82a28c0e745db1b@mail.gmail.com>
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
prev parent reply other threads:[~2008-01-19 4:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 4:12 Siva Velusamy
2008-01-19 4:21 ` Daniel Jacobowitz
2008-01-19 4:26 ` Siva Velusamy
2008-01-19 4:43 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080119044333.GA29595@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=siva.velusamy@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox