It may happen that xbt_log already exited at this point, leading to
erratic segfaults. At least we saw such behavior with the coroutine
factory of the Java world, where MSG_process_get_pid was segfaulting
when called from here.
Better safe than sorry.
**/
void xbt_datadesc_postexit(void)
{
**/
void xbt_datadesc_postexit(void)
{
- XBT_VERB("Exiting DataDesc");
xbt_set_free(&xbt_datadesc_set_local);
xbt_dict_free(&xbt_dd_constants);
xbt_set_free(&xbt_datadesc_set_local);
xbt_dict_free(&xbt_dd_constants);
- XBT_DEBUG("Exited DataDesc");
}
/** This is mainly to debug */
}
/** This is mainly to debug */