From: Gerald Champagne <gerald.champagne@esstech.com>
To: Linux Mips Mailing List <linux-mips@linux-mips.org>
Subject: tools for modifying dwarf symbols
Date: 12 Sep 2002 17:30:59 -0500 [thread overview]
Message-ID: <1031869864.7173.84.camel@localhost.localdomain> (raw)
Is there a tool that will allow me to modify the path of filenames in
dwarf symbols in an elf file? I've looked at everything in binutils,
but these tools only manipulate the binary portion of elf files. I
don't see any similar tools for modifying dwarf debug symbols in an elf
file.
My problem is that my debugger can't read the source files when absolute
paths are used in filenames. In my environment, I have to compile on
one system using one path to the files, then later I have to access the
same data from the debugger using a different path. This works when the
filenames are embedded using relative paths. Larger systems like the
linux kernel or the pmon boot loader use absolute path names everywhere
in the makefiles. These absolute paths are embedded in the elf file and
my debugger gets confused.
Is there a tool or library that will simplify manipulating the dwarf
data in the elf files?
Thanks,
Gerald
reply other threads:[~2002-09-12 22:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1031869864.7173.84.camel@localhost.localdomain \
--to=gerald.champagne@esstech.com \
--cc=linux-mips@linux-mips.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