[RFC] package.bbclass and aggressive library stripping

[RFC] package.bbclass and aggressive library stripping

[Josh Mahonin]

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?

Regards,

Josh

Re: [RFC] package.bbclass and aggressive library stripping

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLdYfKMkyGM64RGpERAmYtAKC19axatS/rXey8T0dWJuCqaEMTvwCgpwjB
4obElqukiYX3iGloqdR0k5g=
=5icm
-----END PGP SIGNATURE-----

Re: [RFC] package.bbclass and aggressive library stripping

[Denys Dmytriyenko]

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.

-- 
Denys

Re: [RFC] package.bbclass and aggressive library stripping

[Khem Raj]

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