From: Daniel Berlin <dan@cgsoftware.com>
To: Richard Henderson <rth@redhat.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [RFC] Partial support for dwarf3 DW_AT_ranges
Date: Fri, 04 Jan 2002 07:20:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0201041020020.21870-100000@dberlin.org> (raw)
In-Reply-To: <20011231003448.A3399@redhat.com>
On Mon, 31 Dec 2001, Richard Henderson wrote:
> GCC began emitting DW_AT_ranges back in September to deal with
> lexical scopes made discontiguous by basic block reordering.
>
> As of today, it may also create discontiguous lexical scopes
> due to scheduling. (Before today under the same circumstances
> we'd lose track of which instructions belonged to which scope
> and fail to emit any debug information whatsoever.)
>
> However, GDB doesn't recognize DW_AT_ranges as a valid way of
> marking a lexical scope, which causes it to discard the scope
> entirely. Which is probably the least useful thing that could
> be done.
>
> The following does not add proper support for discontiguous
> address ranges. I couldn't figure out how to do that in any
> way that wasn't horribly invasive.
Horribly invasive to the dwarf2 reader, or to other pieces of gdb?
next prev parent reply other threads:[~2002-01-04 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 0:34 Richard Henderson
2002-01-04 7:20 ` Daniel Berlin [this message]
2002-01-04 9:13 ` Daniel Jacobowitz
2002-01-04 9:48 ` Richard Henderson
2002-01-04 9:47 ` Elena Zannoni
2003-01-29 15:53 ` Daniel Jacobowitz
2003-01-29 18:09 ` Elena Zannoni
2003-01-29 21:27 ` Daniel Jacobowitz
2003-01-29 22:44 ` Daniel Jacobowitz
2003-02-04 14:59 ` Elena Zannoni
2003-02-04 15:05 ` Daniel Jacobowitz
2003-01-30 0:51 ` Daniel Jacobowitz
2003-01-30 1:02 ` Elena Zannoni
2003-01-30 1: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=Pine.LNX.4.33.0201041020020.21870-100000@dberlin.org \
--to=dan@cgsoftware.com \
--cc=gdb-patches@sources.redhat.com \
--cc=rth@redhat.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