News for hackers. Stuff that matters.
Re:Why would you still want to use strace in 2023? [video] by eesmith on Monday January 08, 2024 @06:04AM (#38910437)
Is your example situation really all that common?

If so, what format do you expect for the output?

If it's one filename-per-line then how do you encode filenames with embedded newlines?

How do you encode non-UTF8 characters, or is the file meant to be parsed only in binary mode?

I don't know of any generally agreed upon spec for this, so no matter what you think is right, most people are going to have to write a special-purpose parser.

In which case you might as well parse the native strace output since one is about as complex as the other.

Re:Why would you still want to use strace in 2023? [video] by amelius on Monday January 08, 2024 @07:55AM (#38911271)
It can use the same format as the Unix find utility. This utility has a -print0 flag to separate filenames by NUL characters instead of newlines if desired.
Re:Why would you still want to use strace in 2023? [video] by eesmith on Monday January 08, 2024 @11:02AM (#38913906)
That is a good point.

I still don't see it as common use case.