Bug Fix Advisory ltrace bug fix update

Advisory: RHBA-2009:1001-1
Type: Bug Fix Advisory
Severity: N/A
Issued on: 2009-05-18
Last updated on: 2009-05-18
Affected Products: Red Hat Desktop (v. 4)
Red Hat Enterprise Linux AS (v. 4)
Red Hat Enterprise Linux ES (v. 4)
Red Hat Enterprise Linux WS (v. 4)
OVAL: N/A

Details

Updated ltrace packages that fix several bugs are now available.

The ltrace utility is a debugging program that runs a specified command
until the command exits. While the command is executing, ltrace intercepts
and records both the dynamic library calls called by the executed process
and the signals received by the executed process. The ltrace utility can
also intercept and print system calls executed by the process.

This update brings following updates:

* ltrace was not able to trace a binary that was called using the "exec"
system call. With this update, ltrace is now able to do so.

* the ltrace(1) man page incorrectly claimed that ltrace could not trace
64-bit binaries.

* on the ItaniumĀ® architecture, a SIGILL signal was occasionally delivered
as a valid signal that informed ltrace about events in the traced binary.
However, ltrace misinterpreted the SIGILL as a signal delivered to the
traced binary.

* IBM System z machines newly support functions with five or more
arguments, which caused ltrace to crash when attempting to trace binaries
called with five or more arguments. This has been fixed with this update
and ltrace now works as expected.

* when ltrace was invoked with the "show summary" ('-c') switch, it
incorrectly did not report the summary to the file provided as an argument
to the '-o' option, but instead to standard output. This has been fixed so
that "ltrace -c" now outputs the summary to the file indicated in the
presence of the '-o' option, thus resolving the issue.

Users of ltrace are advised to upgrade to these updated packages.


Solution

Before applying this update, make sure that all previously-released
errata relevant to your system have been applied.

This update is available via Red Hat Network. Details on how to use
the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/docs/DOC-11259

Updated packages

Red Hat Desktop (v. 4)

SRPMS:
ltrace-0.4-6.el4.src.rpm     ba6af6a42cc5a32235526c959084350f
 
IA-32:
ltrace-0.4-6.el4.i386.rpm     54ff25c7cf23a0e62ba7035d814ea4ea
 
x86_64:
ltrace-0.4-6.el4.x86_64.rpm     21fcee5dec3d0761e99ea9f830370af7
 
Red Hat Enterprise Linux AS (v. 4)

SRPMS:
ltrace-0.4-6.el4.src.rpm     ba6af6a42cc5a32235526c959084350f
 
IA-32:
ltrace-0.4-6.el4.i386.rpm     54ff25c7cf23a0e62ba7035d814ea4ea
 
IA-64:
ltrace-0.4-6.el4.ia64.rpm     3b2b734172fcd99fea2cd468d995ee42
 
PPC:
ltrace-0.4-6.el4.ppc.rpm     e80cd5f114e6ddffd987e7234152af5d
ltrace-0.4-6.el4.ppc64.rpm     a97dc838c5c5579e4018b792ab554df5
 
s390:
ltrace-0.4-6.el4.s390.rpm     85d6f054bd92f40be49a168ed31dae09
 
s390x:
ltrace-0.4-6.el4.s390x.rpm     86bcee028fae258aad21b9fea2a28eac
 
x86_64:
ltrace-0.4-6.el4.x86_64.rpm     21fcee5dec3d0761e99ea9f830370af7
 
Red Hat Enterprise Linux ES (v. 4)

SRPMS:
ltrace-0.4-6.el4.src.rpm     ba6af6a42cc5a32235526c959084350f
 
IA-32:
ltrace-0.4-6.el4.i386.rpm     54ff25c7cf23a0e62ba7035d814ea4ea
 
IA-64:
ltrace-0.4-6.el4.ia64.rpm     3b2b734172fcd99fea2cd468d995ee42
 
x86_64:
ltrace-0.4-6.el4.x86_64.rpm     21fcee5dec3d0761e99ea9f830370af7
 
Red Hat Enterprise Linux WS (v. 4)

SRPMS:
ltrace-0.4-6.el4.src.rpm     ba6af6a42cc5a32235526c959084350f
 
IA-32:
ltrace-0.4-6.el4.i386.rpm     54ff25c7cf23a0e62ba7035d814ea4ea
 
IA-64:
ltrace-0.4-6.el4.ia64.rpm     3b2b734172fcd99fea2cd468d995ee42
 
x86_64:
ltrace-0.4-6.el4.x86_64.rpm     21fcee5dec3d0761e99ea9f830370af7
 
(The unlinked packages above are only available from the Red Hat Network)

Bugs fixed (see bugzilla for more information)

483309 - [4.8] When executing ltrace command with both -o and -c option, the result of ltrace command is not output into file.


Keywords

crash, execl, ia64, ltrace, man, page, s390, sigill


These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package

The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/