From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Previous discussions about recording accurate code ranges in psymtabs?
Date: Wed, 19 Nov 2003 18:58:00 -0000 [thread overview]
Message-ID: <20031119185810.GA10379@nevyn.them.org> (raw)
In-Reply-To: <20031119183904.GE1067@gnat.com>
On Wed, Nov 19, 2003 at 10:39:04AM -0800, Joel Brobecker wrote:
> I was looking at the current code and trying to figure out how to
> modify GDB to record accurate code ranges in its psymtabs instead
> of the textlow/texthigh pair. It looks like it's going to be a major
> change, so I'm trying to find a path that would allow for a transition
> rather than a gigantic patch.
>
> Daniel mentioned that this has been discussed before. Any pointer to
> these discussions? I found some discussions, but they seemed to make
> a decision to move the opposite way: "Remove live range support"...
Jim Blandy posted a proposed interface for describing the ranges, but I
can't find the subject now. And live ranges are something completely
different :) More like .debug_loc location lists, really.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-11-19 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 18:39 Joel Brobecker
2003-11-19 18:52 ` Elena Zannoni
2003-11-19 18:58 ` 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=20031119185810.GA10379@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.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