On 04/21/2013 08:20 AM, Wayne Booth wrote:
> A valgrind log snip after adding
>
> --trace-syscalls=yes -v -v -v -d -d -d
>
> Can be seen at: http://pastebin.com/wZb2vbye
> From what I can tell, it looks like the process is started, but nothing
> happens after that?
Apparently so; after
SYSCALL[7582,2]( 11) sys_execve (
0x806a594(/tmp/opendias_test/bin/opendias_worker), 0x72b2eb0, 0xbeb9c10c
)SYSCALL[7580,2](162) ... [async] --> Success(0x0:0x0)
there are no "SYSCALL[7582,".
But was that because:
1) valgrind printed the pre-syscall message for execve,
but never actually performed the syscall?
2) valgrind did perform the execve, but the system
did not run process 7582 after the execve?
3) valgrind did not run process 7582 after the execve?
Therefore we need an independent observer, namely strace.
[On a side note, the protocol involving file descriptor 7 after the fork()
and before the execve() was hard to follow. Is everything OK there?]
--
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
