0xC0000005: 0x0000000000000000 access violation...

Robert M. Münch robert.muench at saphirion.com
Sun Jul 1 22:04:05 UTC 2018


On 2018-07-01 09:05:56 +0000, Robert M. Münch said:

> This one look nasty...

And it was... the problem was, that I kept D allocated pointers in C 
code without informing the GC that the memory can't be collected nor 
moved. Bridging from D to C and back, is pretty tricky to not miss any 
allocated memory.

Couldn't such a problem be mitigated with an annotation like 
@externalRef or so, which would add the code to protect such memory 
from being GC? It would make the code much more explicit.

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster



More information about the Digitalmars-d-learn mailing list