From: Gary Thomas <gary@mlbassoc.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: Missing debug info
Date: Sun, 03 Apr 2011 14:12:08 -0600 [thread overview]
Message-ID: <4D98D498.10905@mlbassoc.com> (raw)
In-Reply-To: <4D98D0EB.1070802@windriver.com>
On 04/03/2011 01:56 PM, Mark Hatle wrote:
> On 4/3/11 9:53 AM, 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...
>>
>> Thanks
>>
>
> Do the libraries in question have corresponding -dbg package that are empty? Or
> is there stuff in there, it's just incomplete?
>
> What I'm trying to understand is were these items stripped during the recipe
> build, or when they're supposed to be by the package.bbclass into the regular
> and dbg packages.
Ah, interesting. The openssl package does have a -dbg version, but not for
libopenssl nor libcrypto (which were built by the same source package). Any
ideas how/why that happened? I didn't see any magic in the build arguments,
but it's a pretty complex package so I might have missed something.
Just to see what I could learn from this, I tried to install openssl-dbg and got this:
Downloading file:/home/local/p60_poky/tmp/deploy/ipk/armv7a/openssl-dbg_0.9.8p-r3_armv7a.ipk.
openssl-dbg: unsatisfied recommendation for libcrypto-dbg
openssl-dbg: unsatisfied recommendation for libssl-dbg
Installing openssl (0.9.8p-r3) to root...
Downloading file:/home/local/p60_poky/tmp/deploy/ipk/armv7a/openssl_0.9.8p-r3_armv7a.ipk.
Configuring openssl.
Configuring openssl-dbg.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-04-03 20:12 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 [this message]
2011-04-04 13:07 ` Hatle, Mark
2011-04-04 13:36 ` Gary Thomas
2011-04-03 21:46 ` Richard Purdie
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=4D98D498.10905@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=mark.hatle@windriver.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.