Bug 115299 - Completely broken
Completely broken
Product: Fedora
Classification: Fedora
Component: ltrace (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
: 116565 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2004-02-10 08:37 EST by Tim Waugh
Modified: 2007-11-30 17:10 EST (History)
4 users (show)

See Also:
Fixed In Version: 0.3.32-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-04-22 09:54:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2004-02-10 08:37:33 EST
Description of problem:
The ltrace-0.3.29-1 package seems to be completely useless.  Only
malloc()/free() and sometimes close() is shown.

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

For example:

$ ltrace true
+++ exited (status 0) +++


$ ltrace true
__libc_start_main(0x08048a50, 1, 0xbffdaf84, 0x08049a18, 0x08049a60
<unfinished ...>
setlocale(6, "")                                 = "en_GB.UTF-8"
bindtextdomain("coreutils", "/usr/share/locale") = "/usr/share/locale"
textdomain("coreutils")                          = "coreutils"
__cxa_atexit(0x08048c40, 0, 0, 0xbffdaf84, 0xbffdaef8) = 0
exit(0 <unfinished ...>
__fpending(0x002ae640, 0x002b0ba0, 10, 0x002b0238, 10) = 0
+++ exited (status 0) +++
Comment 1 Jakub Jelinek 2004-04-21 17:30:01 EDT
Seems this is a result of my little optimization in the linker:
ltrace is not clever enough and relies on st_values of SHN_UNDEF
I'll try to rework ltrace to do that differently tomorrow.
Comment 2 Jakub Jelinek 2004-04-21 17:34:55 EDT
*** Bug 116565 has been marked as a duplicate of this bug. ***
Comment 3 Jakub Jelinek 2004-04-22 09:54:40 EDT
Should be fixed in ltrace-0.3.32-2 in rawhide.
Comment 4 Gilbert E. Detillieux 2004-06-14 19:05:41 EDT
It still seems to be broken for "ltrace -p <pid>", i.e. I don't get
any library calls reported in the output (though it does show the
signals that were received by the process).

This is the case both with ltrace-0.3.29-1 from FC1 and
ltrace-0.3.32-2 from FC2.  It used to work properly under RedHat 9, so
something broke since then.
Comment 5 Jay Turner 2004-09-02 01:17:46 EDT
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.