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 86140

Summary: "possible process hang on thread death"
Product: [Retired] Red Hat Linux Reporter: Dave Johnson <dave>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: high    
Version: 7.3CC: fweimer
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-06-24 17:00:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dave Johnson 2003-03-14 19:53:42 UTC
Description of problem:
Threads in glibc have problems exiting appropriately.

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


How reproducible:
Regularly

Steps to Reproduce:
1. run multithreaded app
2. if a thread receives a signal, it hangs
    
Actual results:


Expected results:


Additional info:

It looks like this has been out there for awhile, looked at the SRPMS and it 
doesn't look like fix is included (we see same stack trace as inktomi):

http://bugs.gnu.org/cgi-bin/gnatsweb.pl?debug=&database=glibc&cmd=view+audit-
trail&pr=3501

Comment 1 Ulrich Drepper 2003-04-22 06:10:33 UTC
LinuxThreads has problems with signals, this is nothing new.  Try RHL9 with NPTL
which should handle all these things nicely.

Comment 2 Brian Brock 2003-06-24 17:00:44 UTC
closing.