[gmx-developers] valgrind error on grompp

[Szilárd Páll]

Are we not running valgrind in Jenkins? If that's the case this is
unexpected and likely a bug, right?
--
Szilárd


On Fri, Oct 3, 2014 at 4:49 PM, Viveca Lindahl <vivecal at kth.se> wrote:
> I happened to run 'valgrind grompp' on with release-5-0 (a349e4) and get 1
> error:
>
> ==31504== 1 errors in context 1 of 1:
> ==31504== Syscall param write(buf) points to uninitialised byte(s)
> ==31504==    at 0x5D783B0: __write_nocancel (syscall-template.S:81)
> ==31504==    by 0x5D05A82: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1261)
> ==31504==    by 0x5D06F5B: _IO_do_write@@GLIBC_2.2.5 (fileops.c:538)
> ==31504==    by 0x5D0530F: _IO_file_sync@@GLIBC_2.2.5 (fileops.c:892)
> ==31504==    by 0x5CFA9D1: fflush (iofflush.c:41)
> ==31504==    by 0x5D26AE: gmx_fio_close (in
> /data/viveca/programs/awh/bin/gmx_5)
> ==31504==    by 0x4DFE81: gmx_grompp (in
> /data/viveca/programs/awh/bin/gmx_5)
> ==31504==    by 0x5321DD: gmx::CommandLineModuleManager::run(int, char**)
> (in /data/viveca/programs/awh/bin/gmx_5)
> ==31504==    by 0x48C434: main (in /data/viveca/programs/awh/bin/gmx_5)
> ==31504==  Address 0x404d050 is not stack'd, malloc'd or (recently) free'd
> ==31504==  Uninitialised value was created by a stack allocation
> ==31504==    at 0x4DACFB: gmx_grompp (in
> /data/viveca/programs/awh/bin/gmx_5)
>
> ... comments?
>
>
> Viveca
>
> --
> Gromacs Developers mailing list
>
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> posting!
>
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
>
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers or
> send a mail to gmx-developers-request at gromacs.org.