On Wed, 2024-07-17 at 20:47 +0200, Julian Seward wrote: > > I don't follow the details exactly, but FWIW .. valgrind running an > application is "just another normal process". It has no > understanding > of or special-casing relating to NUMA, or particular cores/nodes in a > multiprocessor machine. That was my understanding also, that each valgrind instance is stand- alone - hence two should run on separate nodes the same as on the same node, but with better access to memory/cpu because they do not have to contend for them on the same node > > > My conjecture is that the valgrind core is one instance of the > > gdbserver, which then spawns the tools, and hence one should not > > force > > Also, there is no gdbserver involved unless you start it with > specific > flags to invoke GDB support. But that is not the default. > > It might be that if you are doing cross-process synchronisation via > accesses to shared memory, that depend on specific details of the > machine's > memory coherence model, that you could wind up with problems. > Something > like that I could believe. > > J > > Yes, there is cross-thread synchronization via shared memory, but not cross-process. I am just running helgrind and drd on exactly the same stand-alone program.
Thanks, Elaine > > _______________________________________________ > Valgrind-users mailing list > Valgrind-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/valgrind-users _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
