Re: Can you run two instances of valgrind on separate nodes in a multi-core NUMA environment?

On Wed, 2024-07-17 at 20:47 +0200, Julian Seward wrote:
> Also, there is no gdbserver involved unless you start it with specific
> flags to invoke GDB support.  But that is not the default.

Note that the option to activate or not the gdbserver in valgrind is:
    --vgdb=no|yes|full        activate gdbserver? [yes]
Default option is yes, which means that the gdbserver is activated but has
no impact on the generated code. With full, the generated code is slower but allows
more precise breakpoints and watchpoints.

Unless you also use e.g. --vgdb-stop-at= or --vgdb-error=XXXX, 
-vgdb=yes should have no visible impact and cause no interaction between
different valgrind processes.

Note that if --vgdb=no is specified, a set of features (such as external control
from the shell, callgrind_control, ...) will not be available (in addition to no 
no debugging).

Thanks
Philippe