From: Daniel Jacobowitz <drow@mvista.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Location list support.
Date: Sat, 01 Feb 2003 16:57:00 -0000 [thread overview]
Message-ID: <20030201165754.GA29615@nevyn.them.org> (raw)
In-Reply-To: <3E3B7C35.6030208@suse.cz>
On Sat, Feb 01, 2003 at 08:50:13AM +0100, Michal Ludvig wrote:
> Hi all,
> this is a first part of my attempt to enable use of dwarf3 .debug_loc
> sections (as generated by GCC's rtlopt-branch) for variable tracking.
> With this patch GDB at least doesn't segfault as it did when trying to
> debug a binary with .debug_loc section.
> It can already read and parse .debug_loc and then use the appropriate
> first block found for a given DIE for obtaining the SYMBOL_VALUE() in
> newsymbol(). So now it behaves exactly like it did with GCCs that didn't
> emit .debug_loc.
> I hope to have a full support (ie. SYMBOL_VALUE that depends on PC)
> available soon.
> This was developped in gdb-5.3 but should be usable with mainline with
> no problems.
>
> Comments? Approvals?
>
> Michal Ludvig
Michal,
Can I ask you to sit on this patch for another two or three days? I'll
have LOC_COMPUTED ready probably on Monday, and after that it would be
easy to take what you've done and use it for proper location lists.
Merging this in now would make my work a lot harder.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-01 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 7:50 Michal Ludvig
2003-02-01 16:57 ` Daniel Jacobowitz [this message]
2003-02-21 11:06 Michal Ludvig
2003-02-21 17:11 ` Daniel Jacobowitz
2003-02-21 23:09 ` Michal Ludvig
2003-02-21 17:47 ` Keith Walker
2003-02-21 18:02 ` 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=20030201165754.GA29615@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
/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