[petsc-dev] valgrind errors in the SUPERLU*

[Satish Balay]

On Sat, 16 Jan 2016, Xiaoye S. Li wrote:

> By the way, I have a question about valgrind.   Lately I have been chasing
> a possible memory corruption on  Cori at NERSC.  Valgrind gave LOTS OF
> internal system-related warnings, such as:
> 
> ==39059== Conditional jump or move depends on uninitialised value(s)
> ==39059==    at 0xD5E336: __register_atfork (register-atfork.c:119)
> ==39059==    by 0xD5E418: __libc_pthread_init (libc_pthread_init.c:48)
> ==39059==    by 0x6629E1: __pthread_initialize_minimal (nptl-init.c:462)
> ==39059==    by 0xD14BDA: (below main) (libc-start.c:152)
> ==39059==
> ==39057==    by 0xD5E418: __libc_pthread_init (libc_pthread_init.c:48)
> ==39057==    by 0x6629E1: __pthread_initialize_minimal (nptl-init.c:462)
> ==39057==    by 0xD14BDA: (below main) (libc-start.c:152)
> 
> ​This has nothing do do with my program.  Do you know a way to NOT to print
> those?   I got a huge file filled with these, hard to find out the real
> error.

You can ask valgrind to create a supression file.

[then edit this file - and format it to include only the stuff that you want to supress]

And then - use this file for your next run - to catch the actual issues.

https://wiki.wxwidgets.org/Valgrind_Suppression_File_Howto has some of this info..


We normally recommend using valgrind on linux with mpich built with
'--enable-g=meminit' [--download-mpich option with petsc configure
defaults to this mode] - so that its valgrind clean - and not bother
with supression files.

Satish