From: Stephen & Linda Smith <ischis2@cox.net>
To: gdb@sourceware.org
Subject: Stripped files
Date: Wed, 10 Jan 2007 01:26:00 -0000 [thread overview]
Message-ID: <45A44256.1070004@cox.net> (raw)
We've had a couple of discussions about stripped files here lately and
so I want to know a couple of things from GDB's point of view.
Am I breaking any assumptions in the GDB code if the code running on a
remote target is stripped and the code that GDB loads on the host has
the symbolic information? In other words is GDB likely to get confused
by this situation?
If the situation in the above paragraph isn't a problem, would it be a
good idea for GDB to sniff for the file with the symbolic information
via an default extension. For example the file that would be on the
remote target would be something like libfoo.so and the file that that
gdb would look for first on the host system would be
libfoo.so-withsymbols and then fi that didn't exist it would look for
libfoo.so.
What do you think of that?
next reply other threads:[~2007-01-10 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 1:26 Stephen & Linda Smith [this message]
2007-01-10 2:52 ` Daniel Jacobowitz
2007-01-10 4:45 ` Stephen & Linda Smith
2007-01-10 14:05 ` 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=45A44256.1070004@cox.net \
--to=ischis2@cox.net \
--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