Bug 631870 - rpaths with more than one component trigger a valgrind warning
Summary: rpaths with more than one component trigger a valgrind warning
Keywords:
Status: CLOSED DUPLICATE of bug 629976
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Andreas Schwab
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-08 14:56 UTC by Caolan McNamara
Modified: 2016-11-24 15:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-08 15:00:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
standalone demo (431 bytes, application/x-gzip)
2010-09-08 14:56 UTC, Caolan McNamara 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Sourceware 10610 0 None None None Never

Description Caolan McNamara 2010-09-08 14:56:07 UTC 
Created attachment 446003 [details]
standalone demo

Description of problem:
Worrying valgrind warning where there is more than one component in an RPATH, e.g. $ORIGIN/../pathB:$ORIGIN/../pathA

Version-Release number of selected component (if applicable):
glibc-2.12.90-10.x86_64

How reproducible:
100%

Steps to Reproduce:
1. unpack testcase
2. make
  
Actual results:
==17283== Invalid free() / delete / delete[]
==17283==    at 0x4C25D72: free (vg_replace_malloc.c:325)
==17283==    by 0x59126EA: ??? (in /lib64/libc-2.12.90.so)
==17283==    by 0x5B4C817: ??? (in /lib64/libc-2.12.90.so)
==17283==    by 0x5B4C81F: ??? (in /lib64/libc-2.12.90.so)
==17283==    by 0x5B4C827: ??? (in /lib64/libc-2.12.90.so)
==17283==    by 0x7FF00013F: ???
==17283==  Address 0x4053380 is not stack'd, malloc'd or (recently) free'd

Expected results:
Nothing

Additional info:
If it is spurious, throw it over the wall to valgrind for adding to the default suppressions
Comment 1 Jakub Jelinek 2010-09-08 15:00:26 UTC 

*** This bug has been marked as a duplicate of bug 629976 ***
Note You need to log in before you can comment on or make changes to this bug.