GC issue? List.pool overwritten by allocated object
Denis Feklushkin
feklushkin.denis at gmail.com
Wed May 14 08:00:06 UTC 2025
On Wednesday, 14 May 2025 at 06:54:42 UTC, Denis Feklushkin wrote:
> ((p < curr && p_end <= curr) || (p >= curr_end && p_end >=
> curr_end));
The idea of such check failed because List pointers to other
lists sometimes are overwritten by garbage and issue just moves
to curr.next access
I also see that there is no any kind of TLS sections in the
libvulkan.so
But I don't understand why malloc() can give intersecting
allocations in this case. Any ideas?
More information about the Digitalmars-d
mailing list