Changes between Version 8 and Version 9 of DevelopingWithValgrind


Ignore:
Timestamp:
2012-10-03T09:12:18Z (5 years ago)
Author:
peter
Comment:

mention spurious messages from optimizer runs; use -r syntax

Legend:

Unmodified
Added
Removed
Modified
  • DevelopingWithValgrind

    v8 v9  
    2121egrep 'lost:|ERROR SUMMARY:|FILE DESCRIPTORS:' *.err | egrep -v '0 bytes in 0 blocks|0 errors from 0 contexts| 3 open at exit.'
    2222}}}
     23Note that this simple command will produce spurious error messages {{{FILE DESCRIPTORS: 4 open at exit}}} for fork()-based parallel optimizer runs. This is because the child processes need to keep an additional file descriptor open in order not to interfere with the parent process. These messages can safely be ignored.
    2324
    2425I also keep a shell script on my path, called {{{rungrind}}}, which has these contents:
    2526{{{
    26 nice valgrind --leak-check=full  /path/to/cloudy/source/sys_valgrind/cloudy.exe < $1.in >$1.out 2>$1.valgrind
     27nice valgrind --leak-check=full  /path/to/cloudy/source/sys_valgrind/cloudy.exe -r $1 2> $1.valgrind
    2728}}}
    2829