1
1
openmpi/opal/class
George Bosilca 3f466e2915 Small change with large benefits. Until now, in DEBUG mode we keep trace of the file and line number where
an object has been created. I slightly change this behaviour. Now, during the life time of an object (when
the reference count is > 0) we keep the place where the object was created and just before freeing the object
we set the location where the object get destroyed. So when we try to release an already destroyed object
we have the location where it happens (where the object get destroyed for the first time).

This commit was SVN r6428.
2005-07-12 05:26:37 +00:00
..
Makefile.am * rename ompi_hash_table opal_hash_table 2005-07-03 16:52:32 +00:00
opal_free_list.c * rename locking code from ompi to opal 2005-07-03 22:45:48 +00:00
opal_free_list.h * rename locking code from ompi to opal 2005-07-03 22:45:48 +00:00
opal_hash_table.c * fix some remaining ompi references 2005-07-04 00:16:24 +00:00
opal_hash_table.h * fix some remaining ompi references 2005-07-04 00:16:24 +00:00
opal_list.c * rename all the atomic functions from ompi to opal 2005-07-03 21:38:51 +00:00
opal_list.h * rename locking code from ompi to opal 2005-07-03 22:45:48 +00:00
opal_object.c * fix some remaining ompi references 2005-07-04 00:16:24 +00:00
opal_object.h Small change with large benefits. Until now, in DEBUG mode we keep trace of the file and line number where 2005-07-12 05:26:37 +00:00
opal_value_array.c * rename ompi_output to opal_output 2005-07-03 23:31:27 +00:00
opal_value_array.h * rename ompi_output to opal_output 2005-07-03 23:31:27 +00:00