- /* mallocators and memory mess introduced by model-checking do not mix well together:
- * The mallocator will give standard memory when we are using raw memory (so these blocks are killed on restore)
- * and the contrary (so these blocks will leak accross restores)
- */
- if (_surf_do_model_check)
- size = 0;
-
- m = xbt_new0(s_xbt_mallocator_t, 1);
- VERB1("Create mallocator %p", m);
- if (XBT_LOG_ISENABLED(xbt_mallocator, xbt_log_priority_verbose))
- xbt_backtrace_display_current();
+/**
+ * @brief Constructor
+ * @param size size of the internal stack: number of objects the mallocator will be able to store
+ * @param new_f function to allocate a new object of your datatype, called in @a xbt_mallocator_get() when the
+ * mallocator is empty
+ * @param free_f function to free an object of your datatype, called in @a xbt_mallocator_release() when the stack is
+ * full, and when the mallocator is freed.
+ * @param reset_f function to reinitialize an object of your datatype, called when you extract an object from the
+ * mallocator (can be NULL)
+ *
+ * Create and initialize a new mallocator for a given datatype.
+ *
+ * @return pointer to the created mallocator
+ * @see xbt_mallocator_free()
+ */
+xbt_mallocator_t xbt_mallocator_new(int size, pvoid_f_void_t new_f, void_f_pvoid_t free_f, void_f_pvoid_t reset_f)
+{
+ xbt_mallocator_t m;