This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: [Robert Sim <simra@cim.mcgill.ca>] libc/1706: libpthread,multiprocessor linux and fgets/getline
- To: Kaz Kylheku <kaz at ashi dot footprints dot net>
- Subject: Re: [Robert Sim <simra@cim.mcgill.ca>] libc/1706: libpthread,multiprocessor linux and fgets/getline
- From: Robert Sim <simra at cim dot mcgill dot ca>
- Date: Thu, 27 Apr 2000 01:17:27 -0400 (EDT)
- cc: Andreas Jaeger <aj at suse dot de>, libc-alpha Mailinglist <libc-alpha at sourceware dot cygnus dot com>
I tried what you suggested below, but I haven't been able to reproduce the
case where it crashes within a single thread. For the time being, assume
that I was mistaken in claiming that it will crash even when only one
thread is spawned (besides initial and manager). I stand by the
observation that guarding the fgets with a mutex still produces the
bug- this I did manage to reproduce 2 minutes ago. My apologies for the
confusion.
R
On Wed, 26 Apr 2000, Kaz Kylheku wrote:
> On Thu, 27 Apr 2000, Robert Sim wrote:
>
> > Date: Thu, 27 Apr 2000 00:23:46 -0400 (EDT)
> > From: Robert Sim <simra@cim.mcgill.ca>
> > To: Andreas Jaeger <aj@suse.de>
> > Cc: libc-alpha Mailinglist <libc-alpha@sourceware.cygnus.com>
> > Subject: Re: [Robert Sim <simra@cim.mcgill.ca>] libc/1706: libpthread,
> multiprocessor linux and fgets/getline
> >
> > Hi,
> >
> > I have some follow-up on my bug report, and I wasn't sure where or how to
> > post it- my apologies if I am spamming the wrong list.
> >
> > I just want to add that the bug occurs even if the fgets calls are guarded
> > by a mutex and, even worse, even if only a single thread of execution is
> > spawned.
>
> Then it may happen even if you just call that function with the main thread and
> don't call pthread_create. Can you try that?
>
> If it still occurs with the main thread only, can then see whether the problem
> still occurs when you don't link in -pthread.
>
> This is significant, because it could rule out the threading library as the
> cause. There are certain pthread_ functions used by libio which are stubbed
> out when libpthread isn't linked in.
>
--
-------------------------------------
Robert Sim
http://www.cim.mcgill.ca/~simra
So long, and thanks for all the Phish