From: Daniel Jacobowitz <drow@false.org>
To: Fabian Cenedese <Cenedese@indel.ch>
Cc: gdb@sourceware.org
Subject: Re: "Preprocess" dwarf info?
Date: Thu, 18 Jan 2007 16:30:00 -0000 [thread overview]
Message-ID: <20070118163047.GA14402@nevyn.them.org> (raw)
In-Reply-To: <5.2.0.9.1.20070118102453.018662f0@NT_SERVER>
On Thu, Jan 18, 2007 at 10:24:59AM +0100, Fabian Cenedese wrote:
> With dwarf this info is not stored expressively anymore if a symbol
> is of type LOC_COMPUTED or LOC_COMPUTED_ARG. Instead gdb will
> evaluate the dwarf debug "code" to return the value every time. I know
> that there may be symbol "locations" that are not representable with
> just 1 or 2 values. But still values such as register numbers or offsets
> will always be the same.
>
> So is there a way to somehow "preprocess" the dwarf info to get out
> the same info gdb stores when using the stabs info?
At least one type already is preprocessed; look in dwarf2read.c and it
should be easy to find it.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-01-18 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 9:25 Fabian Cenedese
2007-01-18 16:30 ` 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=20070118163047.GA14402@nevyn.them.org \
--to=drow@false.org \
--cc=Cenedese@indel.ch \
--cc=gdb@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