From: Martin Quinson <martin.quinson@loria.fr>
Date: Wed, 17 Oct 2012 20:04:27 +0000 (+0200)
Subject: Ensure that the mallocator are really inactive when running MC
X-Git-Tag: v3_8~42
X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/1f50f809c4d885ff2b2c1a626d69ebb4cea0502f?hp=1f50f809c4d885ff2b2c1a626d69ebb4cea0502f;ds=sidebyside

Ensure that the mallocator are really inactive when running MC

- before, they were created during the preinit and then destroyed when
  MC was activated.
- now, they are created inactive, and activated when the configuration
  stops if MC is still not activated.
- this mandates some changes around the initialization mechanism in
  the whole stack.
  - one hint that it was a good idea is that before, _surf_init_status
    were never reaching the value 2 (meaning "config now forbidden",
    according to the preexisting asserts).
  - Now this value is set from surf_routing when the first element of
    platform is created. This is a horrible hack intermixing the
    layers, but it was already accredited by the parser that
    configuration could occur until the first <AS>, but no later.
  - we now would need a proper way of increasing the init level of
    simgrid.

I hope that this change did not break anything, but much more work
would be mandated to clean the init mess properly.
---