Thank you all, Philippe and John, I've understood. Actually, at each sigtrap in gdb I see an error in valgrind and this is exactly what I needed. I was able to fix my bug. Thanks again.
Marco ________________________________________ Da: Philippe Waroquiers <philippe.waroqui...@skynet.be> Inviato: mercoledì 28 ottobre 2015 23.13 A: Marco Cisternino Cc: valgrind-users@lists.sourceforge.net Oggetto: Re: [Valgrind-users] valgrind and gdb On Wed, 2015-10-28 at 13:23 +0000, Marco Cisternino wrote: > 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" An additional note for what concerns the 'non existent' file: either the libc sources are not installed on your system, or, if they are installed, gdb does not find them. In the last case, you can tell to gdb where to find the files, using the gdb 'dir' command to add a directory to gdb source files search path. Philippe ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
