Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 88336

Summary: nptl SEGV with combination of pthread_cond_wait() / pthread_cond_timedwait() & pthread_exit()
Product: [Retired] Red Hat Linux Reporter: David Watson <dwatson>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: fweimer, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-04-17 04:48:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
Code to demonstate nptl fault none

Description David Watson 2003-04-09 03:24:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
Threaded application segfaulted in Async I/O. This was traced to a fault in
NPTL. Sample code to reproduce fault is attached. Sample code runs fine with
LD_ASSUME_KERNEL=2.2.5.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Compile attached sample with 'gcc -o nptl -lpthread nptl.c'
2.Run nptl
3.
    

Actual Results:  Segmentation Fault

Expected Results:  Success

Additional info:

Comment 1 David Watson 2003-04-09 03:26:07 UTC
Created attachment 91024 [details]
Code to demonstate nptl fault

Comment 2 Jakub Jelinek 2003-04-09 07:08:29 UTC
This ought to be fixed in the proposed glibc bugfix errata.
ftp://people.redhat.com/jakub/glibc/errata/9/

Comment 3 Ulrich Drepper 2003-04-17 04:08:23 UTC
Try glibc-2.3.2-27.9 and let us know.  The program prints "success" for me.

Comment 4 David Watson 2003-04-17 04:48:02 UTC
Fixed in errata.