[Darshan-users] Call to PMPI_Comm_free when DARSHAN_ENABLE_NONMPI is set

[Snyder, Shane]

Hello Ed,

Thanks for reaching out!

We've actually got a fix for this in our master branch currently, so this will be fixed in our next release. If you're able to build based off of master, all should be good.

--Shane
________________________________
From: Darshan-users <darshan-users-bounces at lists.mcs.anl.gov> on behalf of Ed Karrels <edk at illinois.edu>
Sent: Friday, February 5, 2021 4:44 PM
To: darshan-users at lists.mcs.anl.gov <darshan-users at lists.mcs.anl.gov>
Subject: [Darshan-users] Call to PMPI_Comm_free when DARSHAN_ENABLE_NONMPI is set

Hello Darshan team,
When using Darshan to profile a non-MPI application using the DARSHAN_ENABLE_NONMPI flag, the application is crashing with these error messages:

Attempting to use an MPI routine before initializing MPICH
Abort(671693573) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Comm_free: Invalid communicator, error stack:
PMPI_Comm_free(137): MPI_Comm_free(comm=0x996cf0) failed
PMPI_Comm_free(85).: Invalid communicator

This is with darshan-3.2.1.  In darshan-runtime/lib/darshan-core.c line 2039 there is a call to PMPI_Comm_free(&core->mpi_comm) that isn't protected with a check of "using_mpi". Should it be?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/darshan-users/attachments/20210205/b0bd9cc1/attachment.html>