Thank you Paul for your detailed response which gives a clear understanding of valgrind.
Thanks, Gangadhar On Tue, Jun 1, 2021 at 3:18 PM Paul Floyd <pjfl...@wanadoo.fr> wrote: > > > > On 1 Jun 2021, at 06:46, gangadhara reddy chavva < > meetgangadh...@gmail.com> wrote: > > > > Hi, > > > > I am working on network routers where there will be multiple protocols > running as different processes. if i want to attach the valgrind for more > than one process at the same time what is the command/option to use. > > > Hi > > Valgrind does not “attach” to a process, in the same way that debuggers > like GDB do using the ptrace syscall. > > When Valgrind runs, there is only one process - the Valgrind tool. The > guest application “runs” on a virtual machine within Valgrind. And this can > only be done by starting the guest application. Transferring an already > running process image into Valgrind (to be able to “attach”) would be > fraught with serious problems (for instance, memcheck would not have the > history of allocations and the init state of memory, DRD and Helgrind would > not have the history of mutex locking). > > As already mentioned, it is possible to have Valgrind instrument child > processes. > > A+ > Paul > > > > _______________________________________________ > 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
