|
Size: 2213
Comment: Update as of January, 2020
|
← Revision 7 as of 2021-02-19 11:10:04 ⇥
Size: 1869
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| * [[https://lists.strace.io/pipermail/strace-devel/2017-February/005980.html|Color output]] * There's a [[https://lists.strace.io/pipermail/strace-devel/2017-March/006254.html|patch]] available (with hard-coded ANSI escape sequences, though) |
|
| Line 13: | Line 11: |
| * [[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=240945|minimum/maximum beats per minute^W^W^Wtime spent in system call]] | |
| Line 16: | Line 13: |
| * [[https://bugzilla.redhat.com/show_bug.cgi?id=1035433|PID namespace translation]] | |
| Line 23: | Line 19: |
| * More feature requests at [[https://github.com/strace/strace/issues?q=is:issue+is:open+label:enhancement|github]]. |
Command-line option for syncing output to files on every line
Output staging for successful/failed syscalls (-z option)
- Implemented in strace 5.2.
Posssible extension: filtering by specific retval/errno (possible syntax: -e trace=...:{ret,retval,err,errno}{=,!=,<,<=,>,>=,&,!&}VAL)
Print memory related to addresses
Possible syntax: -e dump=syscalls:before=1024:after=512 (similar to dumpio())
Construct PID tree ("process lineage")
Provide information about syscall names and numbers
- Mostly implemented as asinfo tool, needs UI rework
- Path tracing for -e read/write.
- Filtering for specific ioctl (or any other dispatch-like syscall command) numbers.
- ioctls are expecially tricky as one usually wants to trace one or several syscall classes and those are set in the middle of ioctl constant.
- msgid and any other id filters
- uid/gid?
- Combine -o| and -ff by allowing providing '{}' in the popen command line.
More feature requests at github.