Stack overflows not caught by madExcept?
Posted: Fri Nov 01, 2019 12:52 am
I'm using madExcept 4.0.17 and Delphi 10.1 Berlin. We have a subscription to madExcept 5.0 but I've not gotten around to switching over our main application to use it. My bad.
Based on a report from the field, I wrote a simple single form test application that causes a stack overflow due to recursion. I just added a button which has an OnClick handler which calls itself.
When I click the button, after a pause the app just disappears without any error indication. I'm pretty sure earlier Delphi versions would give you a runtime error 202 or an EStackOverflow message but apparently not any more, which is rather unhelpful.
However, If I enable madExcept and try again, the app still just disappears. Is this to be expected? Can madExcept catch these? Is there a setting I'm missing?
Based on a report from the field, I wrote a simple single form test application that causes a stack overflow due to recursion. I just added a button which has an OnClick handler which calls itself.
When I click the button, after a pause the app just disappears without any error indication. I'm pretty sure earlier Delphi versions would give you a runtime error 202 or an EStackOverflow message but apparently not any more, which is rather unhelpful.
However, If I enable madExcept and try again, the app still just disappears. Is this to be expected? Can madExcept catch these? Is there a setting I'm missing?