it's all clear now. thanks.
i made my own modifications to syscallfmt.c and ratrace.c, so that pid
textname and syscallname are printed with every call/ret. also call/ret
are always on their own line.
so i can see this now:
175131 strings.test Tsemacquire = 0 "" 1406064623620695405 140606468362
fixed.
--
cinap
On Mon, 21 Jul 2014 17:41:17 PDT Nick Owens wrote:
>
> hello,
>
> i'm trying to use ratrace to debug a go binary.
> what i don't understand is why records of syscalls sometimes appear on
> top of one another.
>
> here's the output of 'ratrace -c ./strings.test >[2]/tmp/ratrace.log',
> where str
hello,
i'm trying to use ratrace to debug a go binary.
what i don't understand is why records of syscalls sometimes appear on
top of one another.
here's the output of 'ratrace -c ./strings.test >[2]/tmp/ratrace.log',
where strings.test is made with 'go test -c strings'.
http://sprunge.us/aCBG
y
