[Avila] Warning: Problem with libpthread on 0.6 release

[Burns, Darrell]

That is good to know.  I was not aware that the libraries would be
different when building outside the snapgear tree.  Now I have to start
worrying about all of my other libraries =3D[

Thanks for the info!=20

-----Original Message-----
From: Dave [mailto:daveg at unixstudios.net]=20
Sent: Monday, May 22, 2006 4:16 PM
To: Avila
Subject: Re: [Avila] Warning: Problem with libpthread on 0.6 release
Subject: [Avila] And a follow up to this issue..

Another customer had an issue with pthreads and I suggested to replace
the /lib/libpthread.so that is on the ramdisk.gz he is using, with the
one located at /usr/local/arm-linux/lib/be/libpthread.so. This resolved
his problem.

It reminded me that there will likely there will be other library
related issues if the developer is building an application or even a
simple compile of hello world...OUTSIDE of the SnapGear (SG) tree.

I am sure you all are aware that during the SG build a libc and
libpthreads and all related libraries are built INSIDE the SG tree and
are used on the ramdisk.gz.

bash# arm-linux-gcc -o hello hello.c

If a developer cross compiles hello.c using the cross development
environment (/usr/local/arm-linux) such as above, it is being built
using/against the includes and MSB libs of the development environment
and NOT against the target libc/libpthreads located in the SG tree and
in romfs/ and ramdisk.gz

I have not thoroughly checked this out but I would highly suspect that
the library (libc/libpthread/etc/etc) versions in the cross development
environment at /usr/local/arm-linux is different than the target
libraries within the SG tree and on the target ramdisk.gz

Just some food for thought..

Thanks!

-Dave

----- Original Message -----
From: "Burns, Darrell" <dburns1 at ibahn.com>
To: "Avila" <avila at lists.unixstudios.net>
Sent: Monday, May 22, 2006 1:37 PM
Subject: [Avila] Warning: Problem with libpthread on 0.6 release
Subject: [Avila] This bug took about two weeks to track down.  My pthreads were locking
up randomly, but because I was using sockets, I was certain I was doing
something wrong with the TCP stuff.

Well - it turns out that the pthreads were locking up.  I replaced the
libpthread.so.0 that was part of the romfs for gateworks Avila release
0.6, with an older libpthread.so.0 from a MontaVista distribution, and
the problem went away.

So - just a warning to let you know that the libpthread.so.0 has a
serious bug, at least in my environment.  If you are trying to track
down threading problems, even though it is not the usual first step,
mistrust this library.

Darrell Burns
Senior Firmware Engineer
10757 S River Front Parkway, Suite 300
South Jordan, UT 84095

Direct: (801) 563-2023
Email:dburns1 at ibahn.com

---------------------------------------------------------------------
To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
For additional commands, e-mail: avila-help at lists.unixstudios.net

---------------------------------------------------------------------
To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
For additional commands, e-mail: avila-help at lists.unixstudios.net