Unexpected output with -f -e trace=file when tracing the Go compiler
Dmitry V. Levin
ldv at altlinux.org
Tue Jun 30 17:41:45 UTC 2015
On Mon, Jun 29, 2015 at 08:06:03AM +0000, Bryan Matsuo wrote:
> I've stumbled onto some behavior that I believe to be a bug in strace. I
> haven't found any documentation of it so I wanted to report it.
> Every once and a while when tracing the Go (golang) compiler using the -f
> flag system calls that (afaict) should be filtered out with the
> ``trace=file'' expression show up in the output.
> $ ./strace-4.10/strace -f -o strace.log -e trace=file go build
> $ grep 'resumed' strace.log
> 4039 <... select resumed> ) = ? <unavailable>
> The select system call is not in the group of file calls. So I don't think
> this line should show up in the output. Also, there is no matching entry
> point for the call.
Thanks, fixed in v4.10-95-g4b80f34:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 181 bytes
Desc: not available
More information about the Strace-devel