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:
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
Buffer overrun detection works, but provides no stacktrace
Re: Buffer overrun detection works, but provides no stacktra
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
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.
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
So did it help finding a real buffer overrun in your main project?
Re: Buffer overrun detection works, but provides no stacktra
YES!!!!
Love madExcept - Fantastic tool!!!!!
Love madExcept - Fantastic tool!!!!!
Re: Buffer overrun detection works, but provides no stacktra
Glad to hear that!