Hi,
Thanks for your feedback. I've done a run under strace:
wbooth@netbook:~/git/clearscene-src-opendias/test$ strace -f -o
/tmp/strace.out valgrind --trace-syscalls=yes --leak-check=full
--leak-resolution=high --error-limit=no --tool=memcheck --num-callers=50
--log-file=results/resultsFiles/valgrind.out --show-below-main=yes
--track-origins=yes --track-fds=yes --show-reachable=yes
--trace-children=yes /tmp/opendias_test/bin/opendias
And the relevant snip from the strace.out log is here:
http://pastebin.com/gzfamVSX
As you can see (from above), the process is started in:
/home/wbooth/git/clearscene-src-opendias/test
and valgrind is asked to write a log at:
results/resultsFiles/valgrind.out
This is fine for the main process. However, shortly after the original fork
(to become a daemon) the main process changes the working directory to
"/tmp".
As you can see from the strace log, valgrind tries to write to a non
existent log file "/tmp/results/resultsFiles/valgrind.out", cannot,
so finishes up with a "exit_group(1)", which would account for all the
symptoms we've seen.
I've updated my tests to call valgrind referencing suppression and log
files will full paths, and everything is working as expected. Thanks for
your help is resolving this blocker. I don't think that valgrind is doing
anything wrong here, so all good.
Regards
Wayne
------------------------------------------------------------------------------
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
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
