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

[Rob Latham]

On 06/04/2015 02:26 AM, Lisandro Dalcin wrote:
> 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:

That's a good fix.  My only concern is if we hit the limit not because 
it is too small, but because something is going wrong.

Hey, we doubled the value back in 2008.  Maybe we just double it every 
6.5 years and we're fine for a few decades.

==rob

>
> 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;
>
>
>

-- 
Rob Latham
Mathematics and Computer Science Division
Argonne National Lab, IL USA