Bug 62396

Summary: glibc-debug-2.2.5-27 crashes "ls -l"
Product: [Retired] Red Hat Linux Reporter: greg hosler <greg>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: 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: 2002-04-06 07:02:59 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:
Bug Depends On:    
Bug Blocks: 61590    
Attachments:
Description Flags
valgrind output showing where the crash is none

Description greg hosler 2002-03-31 03:40:15 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020314

Description of problem:
installing glibc-debug, and trying to run a program, results in segment
violation. some programs run, some easily crash, reproduceably.



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


How reproducible:
Always

Steps to Reproduce:
1. install glibc-debug-2.2.5-27
2. export LD_LIBRARY_PATH=/usr/lib/debug
3. ls -l will crash:


	

Actual Results:  ls -l crashed

Expected Results:  ls -l shouldn't crash

Additional info:

1) not knowing whether to or not, I tried adding /usr/lib/debug to
/etc/ld.so.conf, and reran ldconfig, but teh results are unchanged.
ls -l still crashes. note that a simple "ls" will work.

2) I ran valgrind to see where it is crashing. It appears that the
problem is in dl-open.c - see attachment
Comment 1 greg hosler 2002-03-31 03:41:24 UTC 
Created attachment 51504 [details]
valgrind output showing where the crash is
Comment 2 Jakub Jelinek 2002-04-05 08:51:57 UTC 
Cannot reproduce this with glibc-debug-2.2.5-28 (the one I have installed on
my box). Do you still have problems with current glibc (2.2.5-30)?
Comment 3 greg hosler 2002-04-06 07:02:55 UTC 
problem fixed in glibc-debug-2.2.5-30