[mpich-devel] Issue with too many calls to MPIR_Add_finalize

[Lisandro Dalcin]

On 3 June 2015 at 21:57, Rob Latham <robl at mcs.anl.gov> wrote:
>
>
> On 05/07/2015 07:45 AM, Lisandro Dalcin wrote:
>>
>> I'm running the testsuite of my Python wrappers with MPICH 3.2b2. The
>> runs are aborting this way:
>
>
> Sorry no one got back to you yet.   I opened a ticket to track this issue
>
> https://trac.mpich.org/projects/mpich/ticket/2272
>

Although I've not tested, this fix should be enough:

diff --git a/src/mpi/init/finalize.c b/src/mpi/init/finalize.c
index f71668b..afebd77 100644
--- a/src/mpi/init/finalize.c
+++ b/src/mpi/init/finalize.c
@@ -65,7 +65,7 @@ typedef struct Finalize_func_t {
 } Finalize_func_t;
 /* When full debugging is enabled, each MPI handle type has a finalize handler
    installed to detect unfreed handles.  */
-#define MAX_FINALIZE_FUNC 32
+#define MAX_FINALIZE_FUNC 64
 static Finalize_func_t fstack[MAX_FINALIZE_FUNC];
 static int fstack_sp = 0;
 static int fstack_max_priority = 0;



-- 
Lisandro Dalcin
============
Research Scientist
Computer, Electrical and Mathematical Sciences & Engineering (CEMSE)
Numerical Porous Media Center (NumPor)
King Abdullah University of Science and Technology (KAUST)
http://numpor.kaust.edu.sa/

4700 King Abdullah University of Science and Technology
al-Khawarizmi Bldg (Bldg 1), Office # 4332
Thuwal 23955-6900, Kingdom of Saudi Arabia
http://www.kaust.edu.sa

Office Phone: +966 12 808-0459