Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed:

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

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, 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

Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed:

--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

Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed:

Hi Julian, Thank you for your reply. I get the same message when I run version 3.10.1. Assertion is at aspacemgr-linux.c:1502 Regards Beckett -Original Message- From: Julian Seward [mailto:jsew...@acm.org] Sent: 15 April 2015 10:07 To: john.osulli...@cloudiumsystems.com;

Re: [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: Julian Seward [mailto:jsew...@acm.org] Sent: 15 April 2015

Re: [Valgrind-users] fuse filesystem syscall deadlocks

Upon tracing valgrind upon suggestions above I found two offending system calls in my code: sys_newstat and sys_statfs. I also verified deadlock lines by running valgrind with vgdb set and stepping through the code. Following patch is the changed I did in valgrind to get these system calls

[Valgrind-users] vex mips-IR: unhandled instruction bytes

Has anyone seen this error in MIPS64 platform running Valgrind 3.10.1? # valgrind /var/www/cgi-bin/view_status.cgi ==1957== Memcheck, a memory error detector ==1957== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==1957== Using Valgrind-3.10.1 and LibVEX; rerun with -h for

Re: [Valgrind-users] Failed to read a valid object file image from memory.

On 14.04.2015 21:24, Philippe Waroquiers wrote: On Tue, 2015-04-14 at 19:26 +0100, João M. S. Silva wrote: What you can further do is to use the memcheck monitor commands to examine the definedness of the variables used on the line where the error is detected. See manual for more info

Re: [Valgrind-users] fuse filesystem syscall deadlocks

On Wed, 2015-04-15 at 16:35 -0400, Atalay Ozgovde wrote: Upon tracing valgrind upon suggestions above I found two offending system calls in my code: sys_newstat and sys_statfs. I also verified deadlock lines by running valgrind with vgdb set and stepping through the code. Following patch is

[Valgrind-users] Valgrind: FATAL: aspacem assertion failed:

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

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/trunk trunk cd trunk ./autogen.sh Then configure/build as normal. J --2993:2:aspacem