From: Daniel Jacobowitz <drow@false.org>
To: Steve Eaton <seaton@novell.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
dits365@gmail.com, gdb@sources.redhat.com
Subject: Re: What exactly does "info sharedlibrary" command show?
Date: Tue, 29 Aug 2006 21:17:00 -0000 [thread overview]
Message-ID: <20060829211717.GA31393@nevyn.them.org> (raw)
In-Reply-To: <44F457AC.742A.00E2.0@novell.com>
On Tue, Aug 29, 2006 at 03:05:19PM -0600, Steve Eaton wrote:
> Now imagine you had to do something useful with the said core file. I
> have to try and match up all of the above shared libraries of various
> versions, or try and get fancy and parse the output and tar up the users
> files. You don't have the luxury of having the -g in every library that
> is run everywhere.
>
> The best I have been able to do is to get the user to open the file in
> gdb and do a
> thread apply all bt, in that way I can fiddle around with different
> versions of shared library files until the stacks look right.
>
> Is there an option that a person could configure to include the so
> files in the core or something equivelent ?
Not that I know of, but it's been suggested for at least Linux in the
past. You may wish to ask your OS vendor to implement this.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-29 21:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 12:03 chen free
2006-08-29 12:40 ` Daniel Jacobowitz
2006-08-29 19:15 ` Mark Kettenis
2006-08-29 19:28 ` Daniel Jacobowitz
2006-08-29 20:06 ` Mark Kettenis
2006-08-29 20:12 ` Daniel Jacobowitz
2006-08-29 21:05 ` Steve Eaton
2006-08-29 21:17 ` Daniel Jacobowitz [this message]
2006-08-29 21:08 ` Mark Kettenis
2006-08-29 21:24 ` Daniel Jacobowitz
2006-08-30 5:22 ` chen free
2006-08-30 12:39 ` Daniel Jacobowitz
2006-08-30 13:24 ` chen free
2006-08-29 12:47 ` Frederic RISS
2006-08-29 13:00 ` chen free
2006-08-29 13:20 ` Frederic RISS
2006-08-29 13:36 ` chen free
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=20060829211717.GA31393@nevyn.them.org \
--to=drow@false.org \
--cc=dits365@gmail.com \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=seaton@novell.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