Bug 71228

Summary: using glibc-debug causes many progs to segfault
Product: [Retired] Red Hat Linux Reporter: Andrew Schultz <ajschult784>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 7.3CC: fweimer
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-12-15 22:29:41 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:
Attachments:
Description Flags
stacktrace from "ls -l" none

Description Andrew Schultz 2002-08-10 17:23:43 UTC 
Description of problem:
I installed the glibc-debug-2.2.5-37 and (when active) many things segfault
(/bin/ls, gdb, etc.)  Some things still work.  Everything works fine with
glibc-2.2.5-37.  I noticed in another bug that the debug glibc requires a 2.4
kernel.  I'm running kernel-2.4.18-5.

How reproducible:
Always

Steps to Reproduce:
1. setenv LD_LIBRARY_PATH /usr/lib/debug
2. ls -l

Actual Results:  segmentation fault (will attach a stacktrace)
Comment 1 Andrew Schultz 2002-08-10 17:25:25 UTC 
Created attachment 69851 [details]
stacktrace from "ls -l"
Comment 2 Andrew Schultz 2002-10-06 07:12:12 UTC 
this is working fine with glibc-2.2.93-5 (RH80)