Re: [Valgrind-users] reply： helgrind use more than 32G memory.

[Philippe W. <phi...@sk...>]

On Tue, 2015-06-16 at 18:53 +0800, 王阳 wrote:

> --8146-- univ_laog_do_GC exit seen  41326 next gc at cardinality 61780
> --8146-- univ_laog_do_GC enter cardinality 61780
> --8146-- VALGRIND INTERNAL ERROR:Valgrind received a signal 11
> (SIGSEGV) -exiting
> --8146-- si_code = 1; Faulting address:0x8031AD000; sp: 0x80317db70
> valgrind :the 'impossible' happened:
>    Killed by fatal signal
The above means Valgrind crashed, for an undetermined reason
(either an internal bug in Valgrind, or alternatively, a bug
in your application that corrupts the memory).
Is your application 'memcheck-clean' ?

Before fixing the above, what you can do then is to capture
the statistics before it crashes, using from a shell:
   vgdb v.info stats
and post the resulting output
(do the above when your application has already consumed a significant
memory, but before it has crashed :).

Philippe