diff options
author | Evan Huus <eapache@gmail.com> | 2013-06-16 01:47:43 +0000 |
---|---|---|
committer | Evan Huus <eapache@gmail.com> | 2013-06-16 01:47:43 +0000 |
commit | 82a13484b3dbf5ae8007226a62e63a2c7c4fc74d (patch) | |
tree | 3b00a890b5e4b14d27c7d42f58995ad56e101ac3 /epan/wmem/wmem_tree.h | |
parent | 28dafa414a5f6c51b41f94622ce5359074a305bc (diff) |
Add warning comment to tree autoreset function about allocator
destruction order, and note that it may need thinking about.
svn path=/trunk/; revision=49952
Diffstat (limited to 'epan/wmem/wmem_tree.h')
-rw-r--r-- | epan/wmem/wmem_tree.h | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/epan/wmem/wmem_tree.h b/epan/wmem/wmem_tree.h index 8df7ab3c36..d98e65c352 100644 --- a/epan/wmem/wmem_tree.h +++ b/epan/wmem/wmem_tree.h @@ -55,6 +55,12 @@ G_GNUC_MALLOC; * master scope, however the data lives in the slave scope. Every time free_all * occurs in the slave scope the tree is transparently emptied without affecting * the location of the structure. + * + * WARNING: The slave scope must be destroyed with wmem_destroy_allocator() + * before the master scope is emptied with wmem_free_all() or + * wmem_destroy_allocator(). + * TODO: Is this a valid limitation? It doesn't affect the common case where + * master is epan_scope and slave is file_scope, but... */ WS_DLL_PUBLIC wmem_tree_t * |