How to debug (potential) GC bugs?

Kagamin via Digitalmars-d-learn digitalmars-d-learn at puremagic.com
Mon Oct 3 02:51:32 PDT 2016


If it's heap corruption, GC has debugging option -debug=SENTINEL 
- for buffer overrun checks. Also that particular stack trace 
shows that object being destroyed is allocated in bin 512, i.e. 
its size is between 256 and 512 bytes.


More information about the Digitalmars-d-learn mailing list