Issues with debugging GC-related crashes #2

Kagamin spam at here.lot
Thu Apr 19 08:10:52 UTC 2018


On Wednesday, 18 April 2018 at 17:40:56 UTC, Matthias Klumpp 
wrote:
> On Wednesday, 18 April 2018 at 10:15:49 UTC, Kagamin wrote:
>> You can call GC.collect at some points in the program to see 
>> if they can trigger the crash
>
> I already do that, and indeed I get crashes. I could throw 
> those calls into every function though, or make a minimal pool 
> size, maybe that yields something...

Can you narrow down the earliest point at which it starts to 
crash? That might identify if something in particular causes the 
crash.


More information about the Digitalmars-d mailing list