Bug 116565
| Summary: | ltrace /bin/true does not list library calls | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Timo Lindfors <lindi> |
| Component: | ltrace | Assignee: | Jakub Jelinek <jakub> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | ||
| 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: | 2006-02-21 19:01:32 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: | |||
*** This bug has been marked as a duplicate of 115299 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |
Description of problem: ltrace for some reason fails to list library calls. Version-Release number of selected component (if applicable): ltrace 0.3.29 linux 2.6.3-1.97 How reproducible: Always. Steps to Reproduce: 1. ltrace /bin/true Actual results: $ ltrace /bin/true +++ exited (status 0) +++ $ Expected results: $ ltrace /bin/true __libc_start_main(0x08048ab4, 1, 0xbffff794, 0x0804876c, 0x080496d0 <unfinished ...> __register_frame_info(0x0804ad04, 0x0804ae48, 0xbffff738, 0x40046f18, 0x40132e48) = 0x080487c4 setlocale(6, "") = "LC_CTYPE=fi_FI;LC_NUMERIC=C;LC_T"... bindtextdomain("sh-utils", "/usr/share/locale") = "/usr/share/locale" textdomain("sh-utils") = "sh-utils" __cxa_atexit(0x08048c64, 0, 0, 0x0804966c, 1) = 0 exit(0 <unfinished ...> ferror(0x40130200) = 0 __fpending(0x40130200, 0x400135cc, 0xbffff794, 0x4003f3fe, 0x40132e48) = 0 __deregister_frame_info(0x0804ad04, 0x400135cc, 0x400137bc, 0x40013d50, 1) = 0 +++ exited (status 0) +++ $ Additional info: Copying an ltrace 0.3.26 binary from a debian box produces the same (incorrect) behavior so the bug probably isn't in ltrace. I do not have root access to the box so I can't experiment with other kernel versions.