Re: GC: Understanding potential sources of false pointers

They are for static data an thread-local storage.

Re: GC: Understanding potential sources of false pointers

On 04/22/2017 08:56 AM, Kagamin wrote: .rdata is fine, but afaik you have only strings there, the rest - .data, .bss, .tls will suffer the same issue. I don't know anything about the various object file sections. :/

Re: GC: Understanding potential sources of false pointers

On Thursday, 20 April 2017 at 20:26:06 UTC, Nick Sabalausky (Abscissa) wrote: (even if it's from a C lib) Same for D: .rdata is fine, but afaik you have only strings there, the rest - .data, .bss, .tls will suffer the same issue.

Re: GC: Understanding potential sources of false pointers

On 04/20/2017 09:00 AM, Kagamin wrote: https://issues.dlang.org/show_bug.cgi?id=15723 Hmm, so apparently embedded data (even if it's from a C lib) can also be a source of false pointers. Thanks, good to know.

Re: GC: Understanding potential sources of false pointers

https://issues.dlang.org/show_bug.cgi?id=15723

Re: GC: Understanding potential sources of false pointers

On Thursday, 20 April 2017 at 02:27:37 UTC, Nick Sabalausky (Abscissa) wrote: According to : "Registers, the stack, and any other memory locations added through the GC.addRange function are always scanned conservatively." 1. Can that be safely

GC: Understanding potential sources of false pointers

According to : "Registers, the stack, and any other memory locations added through the GC.addRange function are always scanned conservatively." 1. Can that be safely assumed to be a canonical list of all possible sources of false pointers? 2. What