|
From: Luka N. <luk...@gm...> - 2011-07-07 07:29:01
|
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 |
|
From: <pa...@fr...> - 2011-07-07 07:55:48
|
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" <luk...@gm...> To: val...@li... 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 Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Luka N. <luk...@gm...> - 2011-07-07 08:02:03
|
Oh ok so this is a valgrind issue. I thought my program does something funny. Btw. what does VG_N_SEGMENTS mean? On Thu, 2011-07-07 at 09:55 +0200, pa...@fr... wrote: > 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" <luk...@gm...> > To: val...@li... > 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 > Val...@li... > 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 > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Alexander P. <gl...@go...> - 2011-07-07 08:12:50
|
Those are parts of the address space (of both Valgrind and your program) You can refer to coregrind/m_aspacemgr/aspacemgr-linux.c for details. On Thu, Jul 7, 2011 at 12:01 PM, Luka Napotnik <luk...@gm...> wrote: > Oh ok so this is a valgrind issue. I thought my program does something > funny. Btw. what does VG_N_SEGMENTS mean? > > On Thu, 2011-07-07 at 09:55 +0200, pa...@fr... wrote: >> 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" <luk...@gm...> >> To: val...@li... >> 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 >> Val...@li... >> 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 >> Val...@li... >> 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 > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > -- Alexander Potapenko Software Engineer Google Moscow |
|
From: WAROQUIERS P. <phi...@eu...> - 2011-07-07 10:16:13
|
>Those are parts of the address space (of both Valgrind and >your program) >You can refer to coregrind/m_aspacemgr/aspacemgr-linux.c for details. >>> 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 A segment is a "big piece of memory" given to Valgrind by the kernel. Valgrind uses mmap to request such a segment. Such segments are used either to implement the malloc replacement (for memcheck) or for memory needed by Valgrind itself or because the program itself calls mmap. It might also be that a segment is needed for each thread stack. But if the thread is destroyed, the thread stack segment should be re-usable for the next thread creation. If you have a lot of threads running simultaneously, this might explain a big list of segments. Are the threads always created with the same stack size ? Are these stack sizes big ? Big stack sizes and/or varying stack sizes could also trigger a bug such as http://bugs.kde.org/show_bug.cgi?id=250101 Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |