Bug 1360259

Summary: ltrace: Crash when run on certain processes with the -S option
Product: Red Hat Enterprise Linux 7 Reporter: Jan Zarsky <jzarsky>
Component: ltraceAssignee: DJ Delorie <dj>
Status: CLOSED ERRATA QA Contact: Martin Cermak <mcermak>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: codonell, cww, dj, emachado, esyr, law, mcermak, mnewsome, plambri, ptalbert, sfroemer, smeyer
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ltrace-0.7.91-16.el7 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1678260 (view as bug list) Environment:
Last Closed: 2020-03-31 19:57:47 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: 1420851, 1473733, 1477664, 1678260, 1710255, 1731204, 1731211, 1734363, 1906601    

Description Jan Zarsky 2016-07-26 11:20:53 UTC 
Description of problem:
When run on certain processes (e.g. dbus) and with the -S option (show system calls), ltrace crashes and kills traced process.

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

How reproducible:
always

Steps to Reproduce:
1. Get PID of dbus, auditd or rsyslogd (just examples)
   # ps -ef | grep -E ^dbus

2. Run ltrace with the -S option
   # ltrace -p <PID> -S

Actual results:
# ps -ef | grep -E ^dbus
dbus     28044     1  0 06:50 ?        00:00:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
# ltrace -S -p 28044
getegid32@SYS(ltrace: fetch.c:287: allocate_integer: Assertion `!"Too many return value classes."' failed.
Aborted
# ps -ef | grep -E ^dbus
#
Comment 20 DJ Delorie 2019-07-24 03:39:47 UTC 
Fixed in ltrace-0.7.91-16.el7
Comment 25 errata-xmlrpc 2020-03-31 19:57:47 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://access.redhat.com/errata/RHBA-2020:1089