Hi, It appears that when the default policy is preferred local, the two instances (one helgrind, one drd) are run on the same node.
I thought I could afford more processor/memory access by forcing the two instances to run on separate nodes. When I succeeded in doing that, one process starts up fine, but is apparently not being run, while the other process proceeds normally. BTW, I am running from /dev/pts in gnome. My conjecture is that the valgrind core is one instance of the gdbserver, which then spawns the tools, and hence one should not force the tools to run on separate nodes. However, once that is done, it becomes difficult to correct without restarting the process that is already running, or maybe even rebooting - too much sunk cost. So I thought to ask this question while I am waiting. Thanks, Elaine _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
