Add assertions to ensure ADD_CALL_CHAIN is called holding the lock
authorIvan Maidanski <ivmai@mail.ru>
Thu, 15 Mar 2018 20:16:36 +0000 (23:16 +0300)
committerIvan Maidanski <ivmai@mail.ru>
Thu, 15 Mar 2018 20:16:36 +0000 (23:16 +0300)
commitd194e44fec13f92baefe66c2e2f14521627a9679
treec041f1b7c26709eee730c1b5cbdd39c69274a419
parentcb963c22aa03c2d6f664ef8d7880852559d52ffd
Add assertions to ensure ADD_CALL_CHAIN is called holding the lock
(code refactoring)

* alloc.c (GC_collect_a_little_inner, GC_allocobj): Add assertion that
the allocation lock is held.
* dbg_mlc.c (GC_store_debug_info_inner): Likewise.
* dbg_mlc.c [DBG_HDRS_ALL] (GC_debug_generic_malloc_inner,
GC_debug_generic_malloc_inner_ignore_off_page): Likewise.
* finalize.c [!GC_TOGGLE_REFS_NOT_NEEDED] (ensure_toggleref_capacity):
Likewise.
* specific.c [USE_CUSTOM_SPECIFIC] (GC_key_create_inner): Likewise.
* alloc.c (GC_allocobj): Remove comment (about the lock).
* dbg_mlc.c [DBG_HDRS_ALL] (GC_debug_generic_malloc_inner): Likewise.
alloc.c
dbg_mlc.c
finalize.c
specific.c