How do I trace that memory error?
Marc
jckj33 at gmail.com
Tue Feb 27 14:37:03 UTC 2018
On Tuesday, 27 February 2018 at 14:06:19 UTC, Nicholas Wilson
wrote:
> On Monday, 26 February 2018 at 18:01:07 UTC, Marc wrote:
>> I've tried both gdb and windbg debugger both it either get a
>> "received signal ?" from gdb or crash the GUI application
>> (windbg).
>> The error is:
>>
>>> core.exception.OutOfMemoryError at src\core\exception.d(696):
>>> Memory allocation failed
>>
>> How do I find out the source of the error?
>
> "received signal ?" seems like the one of the GC signals used
> for stopping threads.
> just get gdb to ignore those.
An attempt to continue results in crash.
I also added in my foreach's body:
> scope(exit) {
> import core.memory : GC;
> GC.collect();
> }
But also doesn't solve the issue.
More information about the Digitalmars-d-learn
mailing list