Bug 1158713

Summary: ltrace assigns wrong names to glibc PLT slots
Product: Red Hat Enterprise Linux 7 Reporter: Petr Machata <pmachata>
Component: ltraceAssignee: Jeff Law <law>
Status: CLOSED ERRATA QA Contact: Martin Cermak <mcermak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: bgollahe, mcermak, mnewsome, ohudlick
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Prior to this update, the ltrace utility incorrectly associated Procedure Linkage Table (PLT) slots with symbols from the symbol table. Consequently, when tracing of a certain symbol was requested, a different symbol could have been traced instead. This bug has been fixed, and initialization of the PLT slot map now works correctly.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 03:30:25 UTC Type: Bug
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: 1110700, 1191021    
Attachments:
Description Flags
Packaging patch none

Description Petr Machata 2014-10-30 00:52:52 UTC
$ ltrace -e free ls
libc.so.6->free(0x5)           = <void>
libc.so.6->free(0x78)          = <void>
libc.so.6->free(0xc)           = <void>
libc.so.6->free(0x308)         = <void>
    
Note the nonsense values passed to free.  The problem is that these are not free calls at all, but malloc calls that are assigned to wrong PLT slots.

Version-Release number of selected component (if applicable):
ltrace-0.7.91-9.el7.x86_64

Additional info:
A fix is available:
http://lists.alioth.debian.org/pipermail/ltrace-commits/Week-of-Mon-20141027/000188.html

Comment 4 Petr Machata 2015-03-05 23:37:46 UTC
Created attachment 998602 [details]
Packaging patch

Comment 8 Martin Cermak 2015-09-18 17:22:24 UTC
Verified against ltrace-0.7.91-14.el7.

Comment 10 errata-xmlrpc 2015-11-19 03:30:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2141.html