> Valgrind 3.11.0 > Ubuntu 13.04 > Intel i7 -4700HQ (Haswell) > gdb version 7.5.91.20130417-cvs-ubuntu
Thank you. This helps set an explicit context, and reduces misunderstandings. > I didn't really understand your question, then I don't know how to answer > you. Sorry. > About gdb commands: when do I have to try them? After the "target remote" one? Yes. After printing the message about "Program received signal SIGTRAP ...", then gdb should be awaiting input, with a "(gdb) " prompt. Enter the gdb commands after the prompt, as shown below: >> 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. (gdb) x/i $pc (gdb) x/15i $pc - 0x20 ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
