>> --2993:2:aspacem Reading /proc/self/maps >> --2993:0:aspacem -1: ANON 0038000000-00382a5fff 2777088 r-x-- SmFixed >> d=0x000 i=8527 o=32768 (0) m=0 /usr/lib/valgrind/memcheck-arm-linux >> --2993:0:aspacem Valgrind: FATAL: aspacem assertion failed: >> --2993:0:aspacem segment_is_sane >> --2993:0:aspacem at m_aspacemgr/aspacemgr-linux.c:1477 (add_segment) >> --2993:0:aspacem Exiting now.
That is a really bizarre failure. I've never seen anything like it before and I can't imagine how it happened. It would be useful to know why sane_NSegment() decided the NSegment wasn't sane. Can you put some debug printing into sane_NSegment ? It's a pretty simple function. The only small detail is, you have to use the following to print stuff: VG_(debugLog)(0, "aspacem", format-string, args ...) J ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
