|
From: Yue C. <yc...@gm...> - 2015-09-08 06:43:39
|
I mean the result from "valgrind --trace-syscalls=yes ./myprogram" VS "truss ./myprogram" are different; NOT "truss valgrind --trace-syscalls=yes ./program" VS "truss ./program". Can I modify some Valgrind source code to mark the syscalls issued from Valgrind itself? On Tue, Sep 8, 2015 at 2:30 AM, Ivo Raisr <ivo...@gm...> wrote: > > > 2015-09-08 8:10 GMT+02:00 Yue Chen <yc...@gm...>: > >> Any approach that can distinguish which syscalls are from the >> application, and which syscalls are from Valgrind itself? >> > > Based solely on 'truss' output, no. > I. > |