From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Shared libaries and core files
Date: Fri, 04 Nov 2011 19:25:00 -0000 [thread overview]
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B225CA6013C@DC-US1MBEX4.global.avaya.com> (raw)
In-Reply-To: <201111041838.12151.pedro@codesourcery.com>
> From: Pedro Alves [pedro@codesourcery.com]
>
> > Naively, I would expect the dynamic loading routines in the process
> > would have to keep track of all the loaded libraries, and GDB could
> > extract from these data structures the complete list of libraries that
> > were loaded at the moment of the process failure.
>
> Correct.
That is good to learn. Is there any simple way, given a core file, to
extract an explicit list of loaded libraries?
Dale
next prev parent reply other threads:[~2011-11-04 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 18:02 Worley, Dale R (Dale)
2011-11-04 18:38 ` Pedro Alves
2011-11-04 19:25 ` Worley, Dale R (Dale) [this message]
2011-11-04 20:40 ` Pedro Alves
2011-11-04 20:54 ` Worley, Dale R (Dale)
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=CD5674C3CD99574EBA7432465FC13C1B225CA6013C@DC-US1MBEX4.global.avaya.com \
--to=dworley@avaya.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).