Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 56396

Summary:	quake3 crash at memset
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <xhejtman>
Component:	glibc	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED NOTABUG	QA Contact:	Aaron Brown <abrown>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.2	CC:	fweimer
Target Milestone:	---
Target Release:	---
Hardware:	athlon
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-11-16 19:17:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2001-11-16 19:16:58 UTC

Description of Problem:
With glibc-2.4.4-19-i686 Quake3 Arena crash with sound enabled on signal
11. Sound disabled works ok. glibc-2.4.4-19-i386 works fine with or without
sound. With gdb I've found out it crash is memset function.

Version-Release number of selected component (if applicable):
glibc-2.4.4.-19-i686


How Reproducible:
always

Steps to Reproduce:
1. enable sound
2. run quake3
3. signal 11 is reported

Actual Results:


Expected Results:


Additional Information:

Comment 1 Jakub Jelinek 2001-11-16 19:20:36 UTC

If it crashes in memtest, it means somebody passed it a wrong pointer or
correct pointer but too large size so that it fell off the cliff.
If there was a bug in memset, you'd notice it far earlier.
So this looks like a quake3 bug.

Comment 2 Andrew Ferguson 2001-11-18 21:22:56 UTC

Quake3 with sound fails with Signal 11 for me with glibc-2.2.4-19 with both the
i386 or i686 versions (this is on an Athlon system). I'm not certain this can be
regarded as strictly a Quake3 bug because using LD_PRELOAD to load a simple
memset() function instead of glibc's causes sound to work. Also, Alan Cox posted
on slashdot that this is probably a glibc optimization bug.