Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 105358 - strace does not display all possible ioctl names
strace does not display all possible ioctl names
Product: Red Hat Raw Hide
Classification: Retired
Component: strace (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Roland McGrath
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-09-25 09:21 EDT by Dmitry V. Levin
Modified: 2007-04-18 12:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-12-14 17:03:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
proposed patch (3.35 KB, patch)
2003-09-25 09:22 EDT, Dmitry V. Levin
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2003:294 normal SHIPPED_LIVE New strace package fixes numerous bugs 2003-12-19 00:00:00 EST

  None (edit)
Description Dmitry V. Levin 2003-09-25 09:21:41 EDT
Solar Designer fixed the ioctl reporting code to report multiple matches (if that is the case). 
Previously, depending on bsearch(3) implementation, strace could favor 
audio ioctls over terminal ones where the numbers conflict (on Linux), 
even though the terminal ioctls are obviously far more common. 
Now it will report them like this: 
ioctl(0, TCGETS or SNDCTL_TMR_TIMEBASE, {B9600 opost isig icanon echo ...}) = 0
Comment 1 Dmitry V. Levin 2003-09-25 09:22:31 EDT
Created attachment 94712 [details]
proposed patch
Comment 2 Roland McGrath 2003-11-13 21:51:33 EST
I've put this patch in.
Comment 3 Dmitry V. Levin 2003-12-14 17:03:01 EST
Applied in strace-4.5.1 
Comment 4 John Flanagan 2003-12-19 12:57:56 EST
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.