Issues with debugging GC-related crashes #2

[Matthias Klumpp]

On Wednesday, 18 April 2018 at 22:12:12 UTC, kinke wrote:
> On Wednesday, 18 April 2018 at 20:36:03 UTC, Johannes Pfau 
> wrote:
>> Actually this sounds very familiar: 
>> https://github.com/D-Programming-GDC/GDC/pull/236
>
> Interesting, but I don't think it applies here. Both start and 
> end addresses are 16-bytes aligned, and both cannot be accessed 
> according to the stack trace (`pbot=0x7fcf4d721010 <error: 
> Cannot access memory at address 0x7fcf4d721010>, 
> ptop=0x7fcf4e321010 <error: Cannot access memory at address 
> 0x7fcf4e321010>`). That's quite interesting too: `memSize = 
> 209153867776`. Don't know what exactly it is, but it's a pretty 
> large number (~194 GB).

size_t memSize = pooltable.maxAddr - minAddr;
(https://github.com/ldc-developers/druntime/blob/ldc/src/gc/impl/conservative/gc.d#L1982 )
That wouldn't make sense for a pool size...

The machine this is running on has 16G memory, at the time of the 
crash the software was using ~2.1G memory, with 130G virtual 
memory due to LMDB memory mapping (I wonder what happens if I 
reduce that...)