[Issue 16469] Segmentation fault in bigAlloc with negative size

[via Digitalmars-d-bugs]

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

--- Comment #3 from Lodovico Giaretta <lodovico at giaretart.net> ---
(In reply to Cédric Picard from comment #2)
> Is it a duplicate? Judging only from gdb backtrace those are different
> issues. I haven't checked in druntime though.

As in the other issue, the problem is that a negative constant becomes a huge
size_t value, which should trigger an OutOfMemoryError, but segfaults instead.
So IMHO it's the same issue. It may well be that the druntime presents the
wrong code in two different places, but it is probably two copies of the same
logic, as enlarging (not in place) and allocating perform the same checks and
the same steps.

But of course anybody is free to reopen this if it's deemed necessary.

--