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 158271

Summary: bad : gdb internal problem
Product: [Fedora] Fedora Reporter: ravi <shrasr>
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: cagney, mattdm
Target Milestone: ---   
Target Release: ---   
Hardware: arm9   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-11 23:40:00 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 ravi 2005-05-20 05:10:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)

Description of problem:

lin-lwp.c:645: internal-error: wait_lwp: Assertion `lp->status == 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

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

How reproducible:

Steps to Reproduce: gdb.threads/schedlock.exp on arm processor

Additional info:

Comment 1 Sitsofe Wheeler 2005-05-21 09:38:28 UTC
I never knew you could get Fedora for ARM machines...

Comment 2 Matthew Miller 2006-07-10 22:59:43 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!

Comment 3 petrosyan 2008-02-11 23:40:00 UTC
Fedora Core 3 is not maintained anymore.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.