Bug 38952

Summary: Segmentation fault in pthread_handle_create using gdb
Product: [Retired] Red Hat Linux Reporter: Matt Domsch <matt_domsch>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: edward_blazek, john_hull, notting
Target Milestone: ---   
Target Release: ---   
Hardware: ia64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-05-15 22:18:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
testapp1.c none

Description Matt Domsch 2001-05-03 14:27:40 UTC
Description of Problem:
On IA-64 Wolverine, when you use gdb to debug a program that uses 
pthread_create(), a segmentation fault occurs in pthread_handle_create() 
on the first call to pthread_create().  This make debugging a threaded 
program with gdb impossible.

How Reproducible:

Steps to Reproduce:

Actual Results:

Expected Results:

Additional Information:
Attached is the file 'testapp1.txt' (in UNIX format) which shows output 
from gdb.

Comment 1 Matt Domsch 2001-05-03 14:28:12 UTC
Created attachment 17228 [details]

Comment 2 Bill Nottingham 2001-05-03 15:12:48 UTC
Can you post the source code?

Comment 3 Matt Domsch 2001-05-03 17:28:04 UTC
Created attachment 17247 [details]

Comment 4 Bill Nottingham 2001-05-03 18:40:58 UTC
Thanks. In any case I just reproduced it *real* fast with xmms. Of course,
that's segfaulting even when GDB isn't involved....

Comment 5 Jakub Jelinek 2001-05-04 09:25:42 UTC
Bill, have you made any progress on it?
If not, I'll jump into it.

Comment 6 Bill Nottingham 2001-05-07 13:58:21 UTC
It's kernel related. Debugging under 2.4.2-2 works fine, under our 2.4.3 +
current ia64 patch fails. I'll try in a minute with 2.4.3-2.14.19, once it's
finished rebooting.

Comment 7 Bill Nottingham 2001-05-15 22:18:42 UTC
This should be fixed with the RC1 kernel.