From: Dmitry Samersoff <dms@samersoff.net>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: bfd way to get list of loaded DSO from coredump
Date: Tue, 04 Feb 2014 19:05:00 -0000 [thread overview]
Message-ID: <52F139FD.2010601@samersoff.net> (raw)
In-Reply-To: <52F136F7.3030300@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Pedro,
Thank you for the response!
Today, I'm using target (ELF or MACH-O) specific code (like
Elf_Internal_Dyn) directly to get list of loaded SOLIBs from coredump
Is there any BFD primitives that allows me to remain platform
independent?
- -Dmitry
On 2014-02-04 22:52, Pedro Alves wrote:
> On 01/26/2014 02:13 PM, Dmitry Samersoff wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> Hi Everybody,
>>
>> What is the best way to get list of shared libraries loaded by
>> process at time of crash using libbfd ? i.e. similar to what
>> "info shared" gdb command does.
>
> You didn't mention the target, but the knowledge of how to extract
> the set of loaded shared libraries is actually in GDB (the solib*
> files), not BFD.
>
- --
Dmitry Samersoff
Saint Petersburg, Russia, http://devnull.samersoff.net
* There will come soft rains ...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJS8Tn9AAoJEHEy08c4gIABu4YIAKY7GUed0B7kvhRXsVIPaZCr
z3DNTAxqs4nIuiPWK9WXf8XB8akOMf0AdW/bIQmlWjqpvHCKnpaojaDOTLgCJ2bE
Fj6fd3E7y9Wrf9l509ggHra1Wq6oLj6/S3x3Wa50O38r3E2nL4li3N0StUTcwfB9
VfBC78YPcwRTU5VxZoNckDQFIwDOWmpeZ5wisyrE8azGVeCvNUJLpX7ajXHlktnS
7UCEdB7gBtCPIAAqPU7yhCHu2Y1EGDgpJHVoRKahJozWO7pQh2ArEB1yvOqqvQPM
febZkdoGtOISpa/1aKB2D/wd/HbcLLN6aiHJzajZN8m5onVyjEKRkU2/E7s6nGs=
=2LtD
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-02-04 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 14:14 Dmitry Samersoff
2014-02-04 18:52 ` Pedro Alves
2014-02-04 19:05 ` Dmitry Samersoff [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=52F139FD.2010601@samersoff.net \
--to=dms@samersoff.net \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
/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