Hi Florian,
Thanks for your input, Yes that patch helps, I have moved past the
previous assert and can now at least run valgrind to the point where I hit:
valgrind: Fatal error at startup: a function redirection
valgrind: which is mandatory for this platform-tool combination
valgrind: cannot
: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed:
Hi Guys,
Thanks for the feedback, I will investigate further regarding the file
system, the system is built using Buildroot, so I will poke around there too
see if I can get to the bottom of it.
Regards
-Original Message-
From
On 28/08/15 15:06, John OSullivan wrote:
I have a problem running valgrind on my embedded system, you can see the
detail below but essentially the problem is that Valgrind fails with:
FATAL: aspacem assertion failed
The problem is caused by valgrind detecting a inode number of zero for libc
On 15.04.2015 15:45, Julian Seward wrote:
--2993:2:aspacemReading /proc/self/maps
--2993:0:aspacem -1: ANON 003800-00382a5fff 2777088 r-x-- SmFixed
d=0x000 i=8527o=32768 (0) m=0 /usr/lib/valgrind/memcheck-arm-linux
This isn't sane, because for an ANON segment we should have
On 15/04/15 16:03, Florian Krohm wrote:
This isn't sane, because for an ANON segment we should have d=0 and i=0
and o=0.
Clearly, this is not an ANON segment but a file segment.
I suggest to change the condition on line 3248 in aspacemgr-linux.c
(refering to 3.10.1 sources) to if (1) and
--2993:2:aspacemReading /proc/self/maps
--2993:0:aspacem -1: ANON 003800-00382a5fff 2777088 r-x-- SmFixed
d=0x000 i=8527o=32768 (0) m=0 /usr/lib/valgrind/memcheck-arm-linux
--2993:0:aspacem Valgrind: FATAL: aspacem assertion failed:
--2993:0:aspacemsegment_is_sane
@lists.sourceforge.net
Subject: Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed:
Could you try that again with the current SVN trunk, please? I don't think
anyone has much enthusiasm to chase down obscure failures on an old version
(3.8.x).
svn co svn://svn.valgrind.org/valgrind
15:13
To: Florian Krohm; John OSullivan; valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed:
On 15/04/15 16:03, Florian Krohm wrote:
This isn't sane, because for an ANON segment we should have d=0 and
i=0 and o=0.
Clearly
Hi,
I am trying to run valgrind on an embedded arm device without success.
The system is built using buildroot-2013.05. The system specifications
are given below the following vargrind output:
# valgrind -d -d
--2993:1:debuglog DebugLog system started by Stage 1, level 2 logging
requested
Could you try that again with the current SVN trunk, please? I don't
think anyone has much enthusiasm to chase down obscure failures on an old
version (3.8.x).
svn co svn://svn.valgrind.org/valgrind/trunk trunk
cd trunk
./autogen.sh
Then configure/build as normal.
J
--2993:2:aspacem
10 matches
Mail list logo
