On Tuesday, 11 July 2017 at 01:34:08 UTC, crimaniak wrote:

I have vibe.d application and long-standing error in it.
For the current moment, I have logs for stdout, stderr, and additional log to write exceptions I catch. This error gives me only the short line in stderr log:

core.exception.InvalidMemoryOperationError@src/core/exception.d(696): Invalid 
memory operation

Also, I use registerMemoryErrorHandler(); (see http://vibed.org/docs#handling-segmentation-faults )

What else can I do to have the stack trace for this error?

I can't debug it because I don't have it on my developer's machine.

See the wiki page about this:


If you can't do all that, look for places you might be allocating in a destructor. The recent GC allocation flag -vgc might help:


Reply via email to