On Fri, 2012-11-16 at 09:09 +0800, lchquan wrote:
By using --vgdb=no, it works .
Good that it bypasses the problem.
Still, there is a latent bug in the mmap area which would be
nice to understand.
I am amazed that the --trace-syscalls=yes did not give any output.
(at least on my setup, it gives
--Original--From: "lchquan"2383242...@qq.com;Date: Thu, Nov 15, 2012 08:55 PMTo: "valgrind-users"valgrind-users@lists.sourceforge.net; Subject: valgrind on cortrex-a9 problemhi : i'm using valgrind 3.8.1 on my arm board and get a problem # /opt/vg/bin/valgrind
==15447== error 22 Invalid argument
==15447== error VG_(am_shared_mmap_file_float_valgrind)
/tmp/vgdb-pipe-shared-mem-vgdb-15447-by-root-on-???
Run with valgrind --trace-syscalls=yes ./maintest (or use strace)
to find the system call which gives the error, and perhaps a hint
about what is
On Thu, 2012-11-15 at 07:49 -0800, John Reiser wrote:
==15447== error 22 Invalid argument
==15447== error VG_(am_shared_mmap_file_float_valgrind)
/tmp/vgdb-pipe-shared-mem-vgdb-15447-by-root-on-???
Run with valgrind --trace-syscalls=yes ./maintest (or use strace)
to find the system
11:49 PMTo: "valgrind-users"valgrind-users@lists.sourceforge.net; Subject: Re: [Valgrind-users] Fw:valgrind on cortrex-a9 problem ==15447== error 22 Invalid argument ==15447== error VG_(am_shared_mmap_file_float_valgrind) /tmp/vgdb-pipe-shared-mem-vgdb-15447-by-root-on-???Run with "valg
By using "--vgdb=no", it works .Thank you.Chris--Original--From: "Philippe Waroquiers"philippe.waroqui...@skynet.be;Date: Fri, Nov 16, 2012 03:48 AMTo: "John Reiser"jrei...@bitwagon.com; Cc: "valgrind-users"valgrind-users@lists.sourceforge.net; Subject: Re:
