I'm having the same problem on a Galaxy Nexus (which also uses the OMAP kernel
like the PandaBoard).
127|root@android:/ # /data/local/Inst/bin/valgrind -v ls
==2943== Memcheck, a memory error detector
==2943== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et
I'm having the same problem on a Galaxy Nexus (which also uses the OMAP kernel
like the PandaBoard).
127|root@android:/ # /data/local/Inst/bin/valgrind -v ls
==2943== Memcheck, a memory error detector
==2943== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==2943== Using
Hi guys,
I get a lot of
==8186== Warning: invalid file descriptor 1019 in syscall open()
and similar with other systen calls (accept socket). It is
always descriptor number 1019, on each run. It seems to be
something with Valgrind. I ran strace and it seems like my
program never uses
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
