On Wed, 2012-07-18 at 01:22 +, Anup wrote:
--4562:1:gdbsrv getpkt (C14); [no ack]
--4562:1:gdbsrv set_desired_inferior use_general 0 found 0x402514BE0 tid 1
lwpid 4562
--4562:1:gdbsrv resume_info thread 4562 leave_stopped 0 step 0 sig 17
stepping
0
--4562:1:gdbsrv stop pc
Effectively, vgdb only has -d option.
In this case, you must give the option -v -d to valgrind so as to
have more trace from the Valgrind gdbserver.
Here is the trace with -v -d options given to valgrind.
==4562== Use of uninitialised value of size 8
==4562==at 0x7AAC2CF: __printf_fp
On Sat, 2012-07-14 at 00:44 +, Anup wrote:
Hi,
I am trying to debug memory corruption in a program by attaching it to
valgrind
gdbserver and GDB (valgrind version 3.7.0).
Command: valgrind --tool=memcheck --vgdb=full --vgdb-error=0 prog
With --vgdb-error=0, Valgrind should stop
Philippe Waroquiers philippe.waroquiers at skynet.be writes:
On Sat, 2012-07-14 at 00:44 +, Anup wrote:
Hi,
I am trying to debug memory corruption in a program by attaching it to
valgrind
gdbserver and GDB (valgrind version 3.7.0).
Command: valgrind --tool=memcheck
Hi,
I am trying to debug memory corruption in a program by attaching it to valgrind
gdbserver and GDB (valgrind version 3.7.0).
Command: valgrind --tool=memcheck --vgdb=full --vgdb-error=0 prog
I am expecting that execution will stop when valgrind detects memory error
which
will allow me to
