Bug 87581
Summary: | Newest glibc causes thread havoc. Cannot debug with GDB any longer | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Elias Israel <eli> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | ezannoni, fweimer |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-04-22 05:59:34 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
Elias Israel
2003-03-29 06:05:01 UTC
The primary problem is a kernel bug which passes incorrect AT_PLATFORM string, so /lib/i686 libraries aren't used. Can you please try ftp://people.redhat.com/jakub/glibc/errata/8.0/*4.80.3* which has workarounds for this (and a couple of bugfixes too)? I downloaded and installed the RPMs you referenced with rpm --upgrade. Now, GDB can start the program, but it still has strange behavior. When the program hits a breakpoint or traps a signal, I get the folllowing: Cannot find user-level thread for LWP 1493: no LWP to satisfy query Attempts to terminate the process being debugged within GDB then get this response: Cannot find thread 32771: invalid thread handle Any new information on this item? Still can't use GDB on threaded programs. Have not been able to reproduce this. Can you reproduce it on some short testcase? What are the exact steps for reproducing it? My bad. Attempting to reproduce the remaining problems turned up a software defect that was masquerading as a similar problem. The "no LWP to satisfy query" should be read as "heap corruption so bad that I wet myself and quit." I consider this bug resolved, thanks. Apparently a user bug. At least in the end. Closing. |