[Valgrind-users] Vlgrind vgdb doesn't stop after memory error

[Anup <anu...@gm...>]

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 debug it using GDB. However, it continues to execute after 
reporting the error. As it is seen in the following snapshot, action on error is 
continue. I want execution to stop at this instance giving control to GDB. 


==31272== Use of uninitialised value of size 8
==31272==    at 0x783AA6C: __mpn_lshift (lshift.S:57)
==31272==    by 0x7851E22: __printf_fp (printf_fp.c:668)
==31272==    by 0x784C19F: vfprintf (vfprintf.c:1616)
==31272==    by 0x7855659: printf (printf.c:35)
==31272==    by 0x4EF2901: gpgpu_sim::cycle() (gpu-sim.cc:1447)
==31272==    by 0x4F77D7D: gpgpu_sim_thread_concurrent(void*) 
(gpgpusim_entrypoint.cc:135)
==31272==    by 0x7B8E9C9: start_thread (pthread_create.c:300)
==31272==    by 0x78EBCDC: clone (clone.S:112)
==31272== 
==31272== (action on error) vgdb me ... 
==31272== Continuing ...


Is this the expected behavior? How can I get valgrind to stop at such points?
I remember using the above command earlier where valgrind stopped on detecting 
memory error, giving control back to GDB. But I am not able to get it working 
again. Is such support available in valgrind at this point?

Any help is appreciated.
Thanks,
Anup