Bug 4602 - minimal program compiled -static -lpthreads dies before main
minimal program compiled -static -lpthreads dies before main
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: binutils (Show other bugs)
6.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Nalin Dahyabhai
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-08-18 18:10 EDT by ctm
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-10-05 12:08:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description ctm 1999-08-18 18:10:55 EDT
/* gcc -static -o test test.c -lpthread */
/* this program will die before it ever gets to main
   using gcc from Red Hat 6.1 */

#include <pthread.h>

static void
not_called (void)
{
  pthread_mutex_unlock (0);
}

int
main (void)
{
  return 0;
}
Comment 1 Jeff Johnson 1999-08-23 13:44:59 EDT
I've reproduced this with
	egcs-1.1.2-17
	glibc-2.1.2-3
on i386. Ditto on sparc with
	egcs-1.1.2-18
	glibc-2.1.2-5
Comment 2 Cristian Gafton 1999-08-27 19:35:59 EDT
assigned to kingdon
Comment 3 Cristian Gafton 1999-08-29 22:03:59 EDT
changed component to binutils - looks like it
Comment 4 Jim Kingdon 1999-08-31 22:59:59 EDT
I have been unable to reproduce this problem with glibc-2.1.2-7
(and the rest of the system being pretty vanilla 6.0).  JBJ, can
you reproduce the problem with -7?  If not, I guess we are done.
If so, can you say a little more about what you mean by "reproduce"
(like maybe there is a system or chroot jail I can just log into
and see for myself?  Or a more detailed recipe?)
Comment 5 Jim Kingdon 1999-10-05 12:08:59 EDT
jbj writes:

  All I did was compile the program and verify that, yes, the
program    did die
  before reaching main. If the problem doesn't occur now, I'd say it's
  fixed. I'd feel better if the mechanism were better understood
  however ...

I just tried it on porky, chroot'd to /mnt/build/6.1, and didn't
have a problem.  This is glibc-2.1.2-12.

I'm going to assume it was a bug in glibc-2.1.2-5 and fixed in -7.

Note You need to log in before you can comment on or make changes to this bug.