Assertion failure in GC_free -- C++ std::vector about bdwgc HOT 2 CLOSED

Only happens if #define GC_DEBUG is set, before including <gc/gc_allocator.h> and <gc/gc_cpp.h>

All the other issues I had with version 7.2 and 7.1 seem to have gone away (as I am using today's version from git). So if I don't set GC_DEBUG everything works great!

(err. sort of great ... I think I now have built cyclic references, which I suspect are not being collected, thus, no premature collection, and no corruption. I'd happily use GC_register_disappearing_link() except that the pointers are deep inside of STL somewhere (specifically, in std::set<Atom*>) so I haven't figured that out just yet...)

from bdwgc.

Assertion failure: malloc.c:506
The relevant part of the stack trace:
# 1 0x00007ffff6dc5b8b in __GI_abort () at abort.c:91
# 2 0x00007ffff7b7bb70 in GC_free (p=) at malloc.c:534
# 3 0x0000000000414c11 in deallocate (__p=, this=, GC_n=) at /usr/local/include/gc/gc_allocator.h:137

Only happens if #define GC_DEBUG is set, before including <gc/gc_allocator.h> and <gc/gc_cpp.h>

Looking into gc-7.2d code, I don't really understand how does deallocate() call GC_free as it should call GC_debug_free (provided GC_DEBUG is defined).

I'm closing the issue for now. If the issue is still reproducible with the fresh master, please let me know.

from bdwgc.