How do I trace that memory error?

[Stefan Koch]

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?

I'd say allocating in a loop is a bad idea :)

perhaps you should start with posting the code that leads to this.