This is the mail archive of the
glibc-linux@ricardo.ecn.wfu.edu
mailing list for the glibc project.
Re: pthreads problems
- To: kd at flaga dot is
- Subject: Re: pthreads problems
- From: Andreas Jaeger <aj at suse dot de>
- Date: 07 Dec 1999 13:52:15 +0100
- Cc: glibc-linux at ricardo dot ecn dot wfu dot edu
- References: <OF4DC8B1A5.66AABD96-ON00256840.00403DF5@flaga.is>
- Reply-To: glibc-linux at ricardo dot ecn dot wfu dot edu
>>>>> kd writes:
> Hi,
> I am having a strange problems with linuxthreads in glibc2.1.2.
> The setup: Linux 2.2.5 for embedded ppc board (MPC823), library Glibc2.1.2
> with cache size patch and soft-float patch applied, glibc2.1.2 compiled
> with gcc 2.95.2 crosscompiler from i386-linux host.
> The problem is that programs using threads hang on pthread_create() call.
> If I run the same program (compiled against glibc 2.1.2) and run it on
> older compilation of glibc version 2.1.1 the programs do not hang on
> pthreads_create but crash instead
> when the last thread stops running. I have though not been able to
> reproduce that behaviour in a simple program but it happens always in the
> more complex c++ code.
> The same programs work fine compiled on a Debian 2.1 system with glibc
> 2.1.2 installed and gcc 2.95.2 or when compiled in vanilla Debian 2.1.
> I know this is vague description of the problem, but because of memory
> constraints I am not able to run gdb on my MPC823 board, and hence unable
> to give stack traces.
> I noticed that there have been some updates to the linuxthreads in the CVS.
Please use the glibc-2-1-branch - don't use the main branch.
> Is it safe for my to get the lates version of linuxthreads (and the new
> linuxthreads_db) directories and
> compile them against the othervise unchanged (sans cache patch) glibc 2.1.2
> source tree or are there changes pthreads related changes in the rest of
> the glibc source tree?
I would be suprised if it works. Just get the whole glibc 2.1.3 CVS
version.
> Or is it just a pipedream that these lates changes might fix this problem I
> am having.
Your report is to vague to say anything.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de