From: Daniel Jacobowitz <drow@false.org>
To: Alejandro Homs <ahoms@cells.es>
Cc: gdb@sourceware.org
Subject: Re: libpython2.4.so: Cannot load symbols for shared library with separate debuginfo
Date: Thu, 07 Jun 2007 13:57:00 -0000 [thread overview]
Message-ID: <20070607135658.GA17949@caradoc.them.org> (raw)
In-Reply-To: <000001c7a907$c3fb73d0$72f95954@cells.es>
On Thu, Jun 07, 2007 at 03:28:38PM +0200, Alejandro Homs wrote:
> Hi,
>
> I am trying to debug a Python C++ extension module. I have installed:
>
> python-2.4-14:
> /usr/bin/python2.4 -> stripped
> /usr/lib/libpython.2.4.so.1.0 -> not stripped
> python-debug-info-2.4.14:
> /usr/lib/debug/usr/bin/python2.4.debug
> /usr/lib/debug/usr/lib/libpython2.4.so.1.0.debug
>
> I installed the latest gdb-6.6. When I load the core file, gdb reads the
> symbols from python2.4.debug, but it does not read the
> libpython2.4.so.1.0.debug with the debug information for the shared library.
> I guess this is because it finds some symbols already on
> libpython2.4.so.1.0, and does not attempt to search the separate debuginfo
> file.
It should always try to load the separate debug file. Is
debug-file-directory set to /usr/lib/debug, and is there a
.gnu_debuglink section in libpython.2.4.so.1.0? You may have
to debug GDB to find out what it thinks it's doing.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-07 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 13:29 Alejandro Homs
2007-06-07 13:57 ` Daniel Jacobowitz [this message]
2007-06-07 15:31 ` Alejandro Homs
2007-06-07 15:39 ` 'Daniel Jacobowitz'
2007-06-07 15:59 ` Andreas Schwab
2007-06-07 17:48 ` Alejandro Homs
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=20070607135658.GA17949@caradoc.them.org \
--to=drow@false.org \
--cc=ahoms@cells.es \
--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