|
From: Karim B. <kar...@gm...> - 2007-08-29 13:28:23
|
Hi I am running valgrind 3.2.3 on a debug version of a program which can exhaust the 3 Go limit of memory when valgrind is used (it can not be run on 64 bit). I have several valgrind tests for it and some of them failed sometimes with : Memcheck: mc_main.c:817 (get_sec_vbits8): Assertion 'n' failed. Memcheck: get_sec_vbits8: no node for address 0x3F3E3DA0 (0x3F3E3DA8) sched status: running_tid=1 Thread 1: status = VgTs_Runnable Thread 2: status = VgTs_WaitSys I don't see invalid read or write in the job. I wondered what was the problem ? and how to trace it ? Thanks Karim |
|
From: Julian S. <js...@ac...> - 2007-08-29 13:36:20
|
> Memcheck: mc_main.c:817 (get_sec_vbits8): Assertion 'n' failed. > Memcheck: get_sec_vbits8: no node for address 0x3F3E3DA0 (0x3F3E3DA8) > > I don't see invalid read or write in the job. I wondered what was the > problem ? and how to trace it ? This is a bug in Memcheck. We have seen it before but do not know the cause. Does this happen only when your program runs out of memory? J |
|
From: Karim B. <kar...@gm...> - 2007-08-29 14:09:40
|
Julian Seward wrote: >> Memcheck: mc_main.c:817 (get_sec_vbits8): Assertion 'n' failed. >> Memcheck: get_sec_vbits8: no node for address 0x3F3E3DA0 (0x3F3E3DA8) >> >> I don't see invalid read or write in the job. I wondered what was the >> problem ? and how to trace it ? >> > > This is a bug in Memcheck. We have seen it before but do not know > the cause. > > Does this happen only when your program runs out of memory? > No I dont think so, I have just checked one and it used 2.5 Gb I could start a job to have more informations. Is there an option for debugging purpose ? > J > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > |
|
From: Karim B. <kar...@gm...> - 2007-08-29 18:13:24
|
Here is a full log file : https://atlas-france.in2p3.fr/Activites/Informatique/TMP_SL4/tmp/RecValgtrig_athenardo_noesdaodtagMemcheck_simpleReco.log Karim Bernardet wrote: > Julian Seward wrote: > >>> Memcheck: mc_main.c:817 (get_sec_vbits8): Assertion 'n' failed. >>> Memcheck: get_sec_vbits8: no node for address 0x3F3E3DA0 (0x3F3E3DA8) >>> >>> I don't see invalid read or write in the job. I wondered what was the >>> problem ? and how to trace it ? >>> >>> >> This is a bug in Memcheck. We have seen it before but do not know >> the cause. >> >> Does this happen only when your program runs out of memory? >> >> > No I dont think so, I have just checked one and it used 2.5 Gb > I could start a job to have more informations. Is there an option for > debugging purpose ? > >> J >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Valgrind-users mailing list >> Val...@li... >> https://lists.sourceforge.net/lists/listinfo/valgrind-users >> >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > |
|
From: Nicholas N. <nj...@cs...> - 2007-08-29 20:17:49
|
On Wed, 29 Aug 2007, Julian Seward wrote: >> Memcheck: mc_main.c:817 (get_sec_vbits8): Assertion 'n' failed. >> Memcheck: get_sec_vbits8: no node for address 0x3F3E3DA0 (0x3F3E3DA8) >> >> I don't see invalid read or write in the job. I wondered what was the >> problem ? and how to trace it ? > > This is a bug in Memcheck. We have seen it before but do not know > the cause. If you can whittle things down to a small test program, we'll have a chance to fix it. Without that, it will be very difficult. Nick |