Page 1 of 1

Buffer overrun detection works, but provides no stacktrace

PostPosted: Thu Feb 02, 2017 11:15 pm
by santiago
Hi madschi,

I started looking into the 'Instantly crash on buffer overrun' (ICOBO) feature.

To test this I just copied the examples for buffer overrun frrom the madExcept help.
I then executed this code.

If the ICOBO feature is not activated nothing happens when this code is executed.
When I enable the ICOBO feature in the MES file, an unhandled exception is caught but it looks like this:

Image

No madExcept box is displayed. No StackTrace.
But madExcept must be active, because this exception only ocurrs when ICOBO is activated.
I then played around with our App and got a similar exception. This is great it means we found a tricky problem, but without a stack trace I would not know where to start looking.

Is this how it is supposed to work?

Thank you!

sb

Re: Buffer overrun detection works, but provides no stacktra

PostPosted: Fri Feb 03, 2017 7:59 am
by madshi
It seems that madExcept exception catching is not active/working. Does it work if you raise a test exception (e.g. "raise Exception.Create('test')")?

Re: Buffer overrun detection works, but provides no stacktra

PostPosted: Fri Feb 03, 2017 2:55 pm
by santiago
Hello madschi,

I figured out the problem. I had mistakenly activated the 'Crash On Buffer Overrun' on the wrong MES file.
I activated it now on the correct MES file.

Sorry for the trouble.

Re: Buffer overrun detection works, but provides no stacktra

PostPosted: Fri Feb 03, 2017 2:58 pm
by madshi
So did it help finding a real buffer overrun in your main project?

Re: Buffer overrun detection works, but provides no stacktra

PostPosted: Fri Feb 03, 2017 8:03 pm
by santiago
YES!!!!
Love madExcept - Fantastic tool!!!!!
:-)

Re: Buffer overrun detection works, but provides no stacktra

PostPosted: Fri Feb 03, 2017 8:10 pm
by madshi
Glad to hear that! 8)