Skip to content

Commit

Permalink
Removed bogus destroy function
Browse files Browse the repository at this point in the history
The data freed in destroy callback actually resides in pkg and not shm memory - this is the original bug.
Now that the data is pkg, makes no sense to free it from the attendant process.

(cherry picked from commit 1e61bdc)
  • Loading branch information
bogdan-iancu committed Mar 30, 2018
1 parent 34dbea5 commit d698e44
Showing 1 changed file with 1 addition and 25 deletions.
26 changes: 1 addition & 25 deletions modules/acc/acc_mod.c
Expand Up @@ -65,7 +65,6 @@ struct tm_binds tmb;
struct rr_binds rrb;

static int mod_init(void);
static void destroy(void);
static int child_init(int rank);


Expand Down Expand Up @@ -295,7 +294,7 @@ struct module_exports exports= {
0, /* extra processes */
mod_init, /* initialization module */
0, /* response function */
destroy, /* destroy function */
0, /* destroy function */
child_init /* per-child init function */
};

Expand Down Expand Up @@ -462,26 +461,3 @@ static int child_init(int rank)
}


static void destroy(void)
{
if (log_extra_tags)
destroy_extras( log_extra_tags);
if (log_leg_tags)
destroy_extras( log_leg_tags);
acc_db_close();
if (db_extra_tags)
destroy_extras( db_extra_tags);
if (db_leg_tags)
destroy_extras( db_leg_tags);

if (aaa_extra_tags)
destroy_extras( aaa_extra_tags);
if (aaa_leg_tags)
destroy_extras( aaa_leg_tags);

if (evi_extra_tags)
destroy_extras( evi_extra_tags);
if (evi_leg_tags)
destroy_extras( evi_leg_tags);
}

0 comments on commit d698e44

Please sign in to comment.