Hi To fix this you will have to build your own Valgrind (if you haven't done so already). Grep for VG_N_SEGMENTS in the source, change it to something bigger and rebuild/reinstall.
A+ Paul ----- Original Message ----- From: "Luka Napotnik" <luka.napot...@gmail.com> To: valgrind-users@lists.sourceforge.net Sent: Thursday, 7 July, 2011 09:28:53 GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: [Valgrind-users] VG_N_SEGMENTS is too low error Hello. I'm running my program under valgrind (3.6.1) and after some time I get the following message and valgrind aborts: --30322:0:aspacem Valgrind: FATAL: VG_N_SEGMENTS is too low. --30322:0:aspacem Increase it and rebuild. Exiting now. Now what could cause such an error? My program can create/destroy threads very quickly. I assume there's something strange with the stack? Any hints why valgrind would complain in such a way? Greets, Luka ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
