From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Missing debug info
Date: Sun, 03 Apr 2011 22:46:02 +0100 [thread overview]
Message-ID: <1301867162.24596.304.camel@rex> (raw)
In-Reply-To: <4D988A05.2070609@mlbassoc.com>
On Sun, 2011-04-03 at 08:53 -0600, Gary Thomas wrote:
> I'm trying to debug some code which uses the openssl library, built from
> the Poky mainline. For some reason (not obvious to me), there is no debug
> info for this library, which makes GDB pretty useless :-(
>
> (gdb) info sharedlibrary
> From To Syms Read Shared Object Library
> 0x40077790 0x4008f60c Yes /tmp/cobra_root/lib/ld-linux.so.3
> 0x401abf80 0x401d57d8 Yes (*) /tmp/cobra_root/usr/lib/libssl.so.0.9.8
> 0x40225548 0x402cfbfc Yes (*) /tmp/cobra_root/usr/lib/libcrypto.so.0.9.8
> 0x400f28f8 0x4010cf90 Yes /tmp/cobra_root/usr/lib/libpcap.so.1
> 0x40326340 0x4040e8d8 Yes /tmp/cobra_root/lib/libc.so.6
> 0x401278fc 0x40128614 Yes /tmp/cobra_root/lib/libdl.so.2
> (*): Shared library is missing debugging information.
>
> Any idea why these libraries don't have debg info? how to get it?
> Rebuilding that library with printf() is pretty tedious...
Looking at some builds here, openssl seems to build debug symbols in the
usual way. Did you have the appropriate -dbg package installed? Are
there debug symbols in /tmp/cobra_root/usr/lib/.debug/libssl.so.0.9.8 ?
Do the files list the same debug checksum?
Cheers,
Richard
next prev parent reply other threads:[~2011-04-03 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 14:53 Missing debug info Gary Thomas
2011-04-03 19:56 ` Mark Hatle
2011-04-03 20:12 ` Gary Thomas
2011-04-04 13:07 ` Hatle, Mark
2011-04-04 13:36 ` Gary Thomas
2011-04-03 21:46 ` Richard Purdie [this message]
2011-04-04 1:25 ` Gary Thomas
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=1301867162.24596.304.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.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