From: "Smith, Stephen \(SWCOE\)" <Stephen.Smith@honeywell.com>
To: "General GDB Mailing List" <gdb@sourceware.org>
Subject: Re: GDB solib interface
Date: Mon, 04 Dec 2006 22:12:00 -0000 [thread overview]
Message-ID: <EF244E26469B2C42B2B72AC465843D6B03B72CB4@AZ18EV808.global.ds.honeywell.com> (raw)
I'm sorry - way back when Kevin asked that I investigate this. So now I
am.
Anyway - Pretend that my "custom" GDB remote.c has been told that a
library has been loaded - what would I need to write to use the solib
interface? Another way of asking the question would be, what would I
need to add to my remote interface file (remote.c) to have it load the
symbols.
I am not looking for a command, per se, just trying to figure out what
functions/structures etc I need to write to have my "custom" GDB load
the libraries symbols.
-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org]
Sent: Monday, December 04, 2006 2:58 PM
To: Smith, Stephen (SWCOE)
Cc: General GDB Mailing List
Subject: Re: GDB solib interface
On Mon, Dec 04, 2006 at 02:55:28PM -0700, Smith, Stephen (SWCOE) wrote:
> I am running GDB to debug a remote application. If I find that a
shared
> library has been loaded, I would like to use the solib interface to
load
> the appropriate shared library symbols.
>
> So lets assume that I have the file name of the shared library, that
was
> just loaded, how do I inform the solib subsystem that to load the
> symbols.
There's no command for this. The solib system is designed for targets
where the target can report that the library was loaded, or where GDB
can otherwise detect it. If you're willing to have a custom GDB for
your platform, you might be able to make it examine the shared library
table in your target, assuming there is one.
--
Daniel Jacobowitz
CodeSourcery
next reply other threads:[~2006-12-04 22:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 22:12 Smith, Stephen (SWCOE) [this message]
2006-12-04 22:25 ` Michael Snyder
2006-12-04 22:29 ` Daniel Jacobowitz
2006-12-04 22:28 ` Daniel Jacobowitz
2006-12-04 22:48 ` Smith, Stephen (SWCOE)
2006-12-04 23:48 ` Michael Snyder
2006-12-05 2:09 ` Smith, Stephen (SWCOE)
2006-12-05 23:03 ` Smith, Stephen (SWCOE)
2006-12-08 21:19 ` Daniel Jacobowitz
2006-12-08 22:23 ` Smith, Stephen (SWCOE)
2006-12-08 23:21 ` Daniel Jacobowitz
2006-12-15 21:12 ` Smith, Stephen (SWCOE)
2006-12-15 22:39 ` Daniel Jacobowitz
2006-12-17 0:42 ` Smith, Stephen (SWCOE)
2006-12-17 2:16 ` Daniel Jacobowitz
2006-12-17 6:37 ` Stephen & Linda Smith
2006-12-17 15:24 ` Daniel Jacobowitz
2006-12-29 22:08 ` Stephen & Linda Smith
2006-12-29 22:54 ` Stephen & Linda Smith
2007-01-04 20:37 ` Smith, Stephen (SWCOE)
2007-01-04 20:38 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2007-01-04 21:32 Smith, Stephen (SWCOE)
2007-01-04 21:40 ` Daniel Jacobowitz
2007-01-04 21:46 ` Smith, Stephen (SWCOE)
2007-01-04 21:49 ` Daniel Jacobowitz
2007-01-05 3:39 ` Stephen & Linda Smith
2007-01-05 3:48 ` Daniel Jacobowitz
[not found] ` <EF244E26469B2C42B2B72AC465843D6B03E34F88@AZ18EV808.global.ds.honeywell.com>
2007-01-05 4:01 ` Daniel Jacobowitz
2007-01-05 19:26 ` Smith, Stephen (SWCOE)
2007-02-07 19:41 ` Smith, Stephen (SWCOE)
2007-02-07 23:57 ` Smith, Stephen (SWCOE)
2006-12-04 21:55 Smith, Stephen (SWCOE)
2006-12-04 21:57 ` 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=EF244E26469B2C42B2B72AC465843D6B03B72CB4@AZ18EV808.global.ds.honeywell.com \
--to=stephen.smith@honeywell.com \
--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