From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Baurzhan Ismagulov <ibr@radix50.net>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Shared libraries and separate debugging files
Date: Thu, 25 Aug 2011 20:12:00 -0000 [thread overview]
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F585B@DC-US1MBEX4.global.avaya.com> (raw)
In-Reply-To: <20110824222150.GM25065@radix50.net>
> From: Baurzhan Ismagulov [ibr@radix50.net]
>
> Debian has it working OOTB. E.g., /lib/libc-2.11.2.so has its
> corresponding /usr/lib/debug/lib/libc-2.11.2.so. FWIW, one can build a
> hello, world and step into printf.
In the situation I am working within, the library files of the
execution host have been copied into a working directory of a
different host for analysis of the core file. So /lib/libc-2.11.2.so
has been copied into /home/foo/crash1/lib/libc-2.11.2.so, and its
debug file is in /home/foo/crash1/usr/lib/debug/lib/libc-2.11.2.so.
But there does not appear to be a way to configure GDP to understand
the connection between the two files.
Dale
next prev parent reply other threads:[~2011-08-25 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 20:02 Worley, Dale R (Dale)
2011-08-24 22:22 ` Baurzhan Ismagulov
2011-08-25 20:12 ` Worley, Dale R (Dale) [this message]
2011-08-25 20:31 ` Jan Kratochvil
2011-08-26 3:40 ` 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=CD5674C3CD99574EBA7432465FC13C1B222B1F585B@DC-US1MBEX4.global.avaya.com \
--to=dworley@avaya.com \
--cc=gdb@sourceware.org \
--cc=ibr@radix50.net \
/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).