> A possible cause could be the page size: as I understand, > mips have different page size setup. > If your valgrind has been compiled with a pagesize > not matching your kernel/setup, then maybe Valgrind might ask > wrongly aligned mmap requests, giving then this EINVAL
Yes, that would be my guess too. At the time the failure happened there was still a block of 1759MB available: | --1956:0:aspacem <<< SHOW_SEGMENTS: out_of_memory (13 segments, 1 [..] | --1956:0:aspacem 6: 0011948000-007f880fff 1759m so it is clearly not the case that it has really run out of memory. 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
