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 +, Marco Cisternino wrote:
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x06018417 in __libc_writev (fd=9, vector=0x6af
On Wed, 2015-10-28 at 13:23 +, Marco Cisternino wrote:
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x06018417 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
On Wed, 2015-10-28 at 13:23 +, Marco Cisternino wrote:
> Then I give gdb
>
> continue
>
> After few seconds gdb says
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x06018417 in __libc_writev (fd=9, vector=0x6af6710, count=3)
> at ../sysdeps/unix/sysv/linux/writev.c:50
>
> 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: wh
one?
Thanks,
Marco
Da: John Reiser
Inviato: mercoledì 28 ottobre 2015 16.28
A: valgrind-users@lists.sourceforge.net
Oggetto: Re: [Valgrind-users] valgrind and gdb
> gdb ./real
> target remote | /usr/local/lib/valgrind/../../bin/vgdb --pid=23498
> continue
> gdb ./real
> target remote | /usr/local/lib/valgrind/../../bin/vgdb --pid=23498
> continue
> After few seconds gdb says
>
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x06018417 in __libc_writev (fd=9, vector=0x6af6710, count=3) at
> ../sysdeps/unix/sysv/linux/writev.c:
