From: Jerome Guitton <guitton@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] dwarf2loc, guard against null
Date: Mon, 17 Sep 2007 12:27:00 -0000 [thread overview]
Message-ID: <20070917122654.GY93930@adacore.com> (raw)
In-Reply-To: <20070917121503.GA7606@caradoc.them.org>
Daniel Jacobowitz (drow@false.org):
> I'm not sure - there must be another bug so it might be this should be
> a gdb_assert instead. The DW_AT_frame_base that brought us here came
> from .debug_info inside an entry for a function. So we must have
> found the function at some point. But we didn't find the function
> this time - why not?
Hmmm... Let me have a closer look. In my case, the problem appears when
debugging an application on VxWorks, with this scenario:
* breakpoint hit;
* print the address of a variable in the current frame (print &DB);
* resume the execution; program exited normally;
* retry to print the variable => end up in dwarf_expr_frame_base,
no frame, crash.
We are (probably) still using a wrong .debug_info at this point.
next prev parent reply other threads:[~2007-09-17 12:27 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 [this message]
2007-09-17 12:30 ` Daniel Jacobowitz
2007-09-17 13:10 ` Jerome Guitton
2007-09-17 13:20 ` Daniel Jacobowitz
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=20070917122654.GY93930@adacore.com \
--to=guitton@adacore.com \
--cc=gdb-patches@sourceware.org \
/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