Likely closure memory corruption

Don turnyourkidsintocash at nospam.com
Mon Mar 4 02:55:57 PST 2013


On Sunday, 3 March 2013 at 16:48:32 UTC, deadalnix wrote:
...
> Obviously, the program segfault soon after that.
>
> It sounds like some memory corruption occurs under the hood. 
> What can I do to work around that bug and to help solving it ?

Have you compiled this with the latest gitHEAD ? Several very 
nasty wrong-code bugs were fixed very recently (eg, bug 9568).


More information about the Digitalmars-d mailing list