Good morning, I can't use valgrind with gdb.
In a terminal I launch my code (real) with valgrind valgrind --vgdb=yes --vgdb-error=0 ./real and valgrind answer me ==23498== (action at startup) vgdb me ... ==23498== ==23498== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==23498== /path/to/gdb ./real ==23498== and then give GDB the following command ==23498== target remote | /usr/local/lib/valgrind/../../bin/vgdb --pid=23498 ==23498== --pid is optional if only one valgrind process is running In another one I launch gdb ./real In gdb I give the command target remote | /usr/local/lib/valgrind/../../bin/vgdb --pid=23498 Then I give gdb continue After few seconds gdb says Program received signal SIGTRAP, Trace/breakpoint trap. 0x0000000006018417 in __libc_writev (fd=9, vector=0x6af6710, count=3) at ../sysdeps/unix/sysv/linux/writev.c:50 50 ../sysdeps/unix/sysv/linux/writev.c: File o directory non esistente. where "non esistente" means "doesn't exist" I don't really know what happens. Could you help me understand, please? Thanks. Best regards, Marco
------------------------------------------------------------------------------
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
