[petsc-users] MUMPS valgrind error
Barry Smith
bsmith at petsc.dev
Mon Nov 20 15:42:19 CST 2023
Looks like memory allocated down in MUMPS and then accessed incorrectly inside MUMPS. Could easily not be PETSc related
> On Nov 20, 2023, at 4:22 PM, Alexander Lindsay <alexlindsay239 at gmail.com> wrote:
>
> This is from a MOOSE test. If I find the same error on something simpler I will let you know
>
> On Mon, Nov 20, 2023 at 12:56 PM Zhang, Hong <hzhang at mcs.anl.gov <mailto:hzhang at mcs.anl.gov>> wrote:
>> Can you provide us a test code that reveals this error?
>> Hong
>> From: petsc-users <petsc-users-bounces at mcs.anl.gov <mailto:petsc-users-bounces at mcs.anl.gov>> on behalf of Alexander Lindsay <alexlindsay239 at gmail.com <mailto:alexlindsay239 at gmail.com>>
>> Sent: Monday, November 20, 2023 2:48 PM
>> To: PETSc <petsc-users at mcs.anl.gov <mailto:petsc-users at mcs.anl.gov>>
>> Subject: [petsc-users] MUMPS valgrind error
>>
>> I recently ran into some parallel crashes and valgrind suggests the issue is with MUMPS. Has anyone else run into something similar recently?
>>
>> ==4022024== Invalid read of size 4
>> ==4022024== at 0xF961266: dmumps_dr_assemble_local (dsol_distrhs.F:301)
>> ==4022024== by 0xF961266: dmumps_scatter_dist_rhs_ (dsol_distrhs.F:169)
>> ==4022024== by 0xF952669: dmumps_solve_driver_ (dsol_driver.F:3677)
>> ==4022024== by 0xF8CA64A: dmumps_ (dmumps_driver.F:2035)
>> ==4022024== by 0xF85E12B: dmumps_f77_ (dmumps_f77.F:291)
>> ==4022024== by 0xF85C30E: dmumps_c (mumps_c.c:485)
>> ==4022024== by 0xEBA8E56: MatSolve_MUMPS (mumps.c:1493)
>> ==4022024== by 0xEE85D97: MatSolve (matrix.c:3631)
>> ==4022024== by 0xF31B060: PCApply_LU (lu.c:169)
>> ==4022024== by 0xF50FD3B: PCApply (precon.c:486)
>> ==4022024== by 0xF511204: PCApplyBAorAB (precon.c:756)
>> ==4022024== by 0xF51C5F0: KSP_PCApplyBAorAB (kspimpl.h:443)
>> ==4022024== by 0xF51C5F0: KSPGMRESCycle (gmres.c:146)
>> ==4022024== by 0xF51C5F0: KSPSolve_GMRES (gmres.c:227)
>> ==4022024== by 0xF5F339D: KSPSolve_Private (itfunc.c:910)
>> ==4022024== Address 0x308b338c is 4 bytes before a block of size 1 alloc'd
>> ==4022024== at 0x4C37135: malloc (vg_replace_malloc.c:381)
>> ==4022024== by 0xF960E93: dmumps_scatter_dist_rhs_ (dsol_distrhs.F:139)
>> ==4022024== by 0xF952669: dmumps_solve_driver_ (dsol_driver.F:3677)
>> ==4022024== by 0xF8CA64A: dmumps_ (dmumps_driver.F:2035)
>> ==4022024== by 0xF85E12B: dmumps_f77_ (dmumps_f77.F:291)
>> ==4022024== by 0xF85C30E: dmumps_c (mumps_c.c:485)
>> ==4022024== by 0xEBA8E56: MatSolve_MUMPS (mumps.c:1493)
>> ==4022024== by 0xEE85D97: MatSolve (matrix.c:3631)
>> ==4022024== by 0xF31B060: PCApply_LU (lu.c:169)
>> ==4022024== by 0xF50FD3B: PCApply (precon.c:486)
>> ==4022024== by 0xF511204: PCApplyBAorAB (precon.c:756)
>> ==4022024== by 0xF51C5F0: KSP_PCApplyBAorAB (kspimpl.h:443)
>> ==4022024== by 0xF51C5F0: KSPGMRESCycle (gmres.c:146)
>> ==4022024== by 0xF51C5F0: KSPSolve_GMRES (gmres.c:227)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20231120/b8ea5eef/attachment.html>
More information about the petsc-users
mailing list