From: Andreas Schwab <schwab@suse.de>
To: "Alejandro Homs" <ahoms@cells.es>
Cc: "'Daniel Jacobowitz'" <drow@false.org>, <gdb@sourceware.org>
Subject: Re: libpython2.4.so: Cannot load symbols for shared library with separate debuginfo
Date: Thu, 07 Jun 2007 15:59:00 -0000 [thread overview]
Message-ID: <jey7ivsr88.fsf@sykes.suse.de> (raw)
In-Reply-To: <000301c7a918$e0de1af0$72f95954@cells.es> (Alejandro Homs's message of "Thu\, 7 Jun 2007 17\:31\:11 +0200")
"Alejandro Homs" <ahoms@cells.es> writes:
> Thanks a lot for your fast response!
>
>> 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.
>
> You are right, the debug-file-directory is pointing to /usr/lib/debug, but
> there is no .gnu_debuglink section in libpython.2.4.so.1.0.
> I am obliged to generate the .gnu_debuglink section?
If there is no debuglink section then the debug info file most likely
does not belong to this library.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-06-07 15:59 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
2007-06-07 15:31 ` Alejandro Homs
2007-06-07 15:39 ` 'Daniel Jacobowitz'
2007-06-07 15:59 ` Andreas Schwab [this message]
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=jey7ivsr88.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ahoms@cells.es \
--cc=drow@false.org \
--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