From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] package.bbclass and aggressive library stripping
Date: Fri, 26 Feb 2010 11:11:05 -0800 [thread overview]
Message-ID: <20100226191105.GB25079@gmail.com> (raw)
In-Reply-To: <20100212181441.GA27392@denix.org>
On (12/02/10 13:14), Denys Dmytriyenko wrote:
> On Fri, Feb 12, 2010 at 05:54:34PM +0100, Koen Kooi wrote:
> > On 12-02-10 16:47, Josh Mahonin wrote:
> > > Hi all,
> > >
> > > I was attempting to use GDB on an OE build, but was given various
> > > warnings about threads being disabled. I've traced the problem to
> > > package.bbclass stripping out necessary symbols in 'libpthread.so.0',
> > > referenced as section 6 in http://sourceware.org/gdb/wiki/FAQ
> > >
> > > I'm admittedly using an out of date OE checkout, but the problem still
> > > appears to be present in trunk as well. Is it better to create a
> > > special case in package.bbclass just for libpthread, or should a
> > > blacklist be created for other potentially affected libraries as well?
> >
> > Installed the appropriate -dbg package works for me
>
> In other words - all the debug symbols are in the corresponding -dbg packages.
> The main packages are stripped to save space on the target - so there is no
> real need to do separate release/debug builds.
libthread_db is special and should not be stripped. I am not sure if gdb is
able to read the symbols from separate debug file for this shared lib.
similarily libpthread.so.1 should not be stripped of the symbol table.
I dont know if we strip out symbol tables too if we do then we should spare
these two libraries.
>
> --
> Denys
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2010-02-26 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 15:47 [RFC] package.bbclass and aggressive library stripping Josh Mahonin
2010-02-12 16:54 ` Koen Kooi
2010-02-12 18:14 ` Denys Dmytriyenko
2010-02-26 19:11 ` Khem Raj [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=20100226191105.GB25079@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.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