From: "Alejandro Homs" <ahoms@cells.es>
To: "'Andreas Schwab'" <schwab@suse.de>
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 17:48:00 -0000 [thread overview]
Message-ID: <000a01c7a92c$0f3cda90$72f95954@cells.es> (raw)
In-Reply-To: <jey7ivsr88.fsf@sykes.suse.de>
> >> 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.
That's a very strange thing. All the other libraries in the same package
have the .gnu_debuglink section. And the debuginfo package was built with
the same timestamp ... I don't know if this was removed intentionally by
SuSE ... I do not have the SRPM of that package, so I will check with recent
package versions.
Anyway, as I said in my previous mail, objcopy did the job, and it works!
Thanks
Alejandro
prev parent reply other threads:[~2007-06-07 17:48 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
2007-06-07 17:48 ` Alejandro Homs [this message]
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='000a01c7a92c$0f3cda90$72f95954@cells.es' \
--to=ahoms@cells.es \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=schwab@suse.de \
/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