Re: How to debug (potential) GC bugs?

[Kagamin via Digitalmars-d-learn]

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.