From: Daniel Jacobowitz <drow@false.org>
To: Jerome Guitton <guitton@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] dwarf2loc, guard against null
Date: Mon, 17 Sep 2007 13:20:00 -0000 [thread overview]
Message-ID: <20070917131951.GA13182@caradoc.them.org> (raw)
In-Reply-To: <20070917131052.GA28874@adacore.com>
On Mon, Sep 17, 2007 at 03:10:52PM +0200, Jerome Guitton wrote:
> When the inferior is dead, target_has_registers (resp.
> target_has_memory, target_has_stack) should be false and
> deprecated_safe_get_selected_frame should return NULL. This is the bug
> in my vxWorks-specific backend (I should pop some target vector at
> mourn_inferior, I guess).
Yes, that's probably it. If you stay connected to the target after
mourning, you may want to look at the new target_mark_exited. I
haven't had time to contribute the target extended-remote bits that
go along with that yet but soon, soon...
> Now back to the original problem: assertion or error? I guess that the
> question is: in which cases get_frame_block can return NULL?
Assertion, please. If we found a frame-relative symbol then it was
certainly within some function associated with a frame. If we can't
find the frame, something has gone wrong.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-17 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 12:04 Jerome Guitton
2007-09-17 12:15 ` Daniel Jacobowitz
2007-09-17 12:27 ` Jerome Guitton
2007-09-17 12:30 ` Daniel Jacobowitz
2007-09-17 13:10 ` Jerome Guitton
2007-09-17 13:20 ` Daniel Jacobowitz [this message]
2007-09-17 13:42 ` Jerome Guitton
2007-09-17 13:52 ` Daniel Jacobowitz
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=20070917131951.GA13182@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.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