Buffer overrun detection works, but provides no stacktrace
Posted: Thu Feb 02, 2017 11:15 pm
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
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