I finally got a stack trace on my InvalidMemoryOperationError

Etienne via Digitalmars-d digitalmars-d at puremagic.com
Thu Jun 4 16:56:26 PDT 2015


Since the application will probably have to stop, might as well 
use the GC:

in GC:

if (gcx.running) {
     gcx.running = false;
     onInvalidMemoryOperationError();
}

in core.exception:

throw new InvalidMemoryOperationError();

And there you go, a beautiful stack trace. I now have a pinpoint 
of the error within 100k++ LOC. Thank you.

Why D? Why fail with a one line message and no debug tools? Why??


More information about the Digitalmars-d mailing list