Program crashes on Windows 11 within Try Except

[PascalDragon]

.....
It means that it will compile, but an except-block might not be entered correctly if at all if an exception occurs.

Like I said, Wow.
So, quick grep through my code, only 36 "except on", less than I'd expect. But quite a variety.  Is there any point in testing ?  I mean, if I simulate, say an EXMLReadError and its correctly handled, can I assume it would always be correctly handled ?

As soon as you have any descendant of the Exception class you don't need to worry anymore, because that will mean that the SysUtils unit will be used and thus everything will be set up correctly. The problem only occurs if the SysUtils unit isn't used anywhere in your whole program.

[dbannon]

OK, thanks for that PD, that is a great relief, I always use SysUtils.

As Bart asked, is this documented somewhere ?  Somewhere where the unwary might find it ?  It does sound like a real corner case but could cause someone a lot of trouble if they did replicate the conditions.

Davo

[Thaddy]

Yes this is documented all over the official documentation so I wonder how you could have missed it.

Is this a case again of ask before you read? You should know better. This question does not belong here because it is wasting time from other people. 

[dbannon]

Yes this is documented all over the official documentation so I wonder how you could have missed it.

Oh, thats good then. Or is it ?

Just to be sure, if Its "all over the official documentation" I suppose its really easy to find. I read through chapter 17 of the Ref, no mention of an unexpected behavior when using Windows to handle an Exception without SysUtils. That seems strange given its "All over".  I also looked in the Wiki and the Help offered when you press F1 in Lazarus. That last Help provided the closest I could find to what we are talking about here Thaddy -

While it is possible to raise an exception with any class descending from TObject, it is recommended to use Exception as the basis of exception class objects: the Exception class introduces properties to associate a message and a help context with the exception being raised. What is more, the SysUtils unit sets the necessary hooks to catch and display unhandled exceptions: in such cases, the message displayed to the end user, will be the message stored in the exception class.

But it does not mention a MSWindow specific problem, does not mention SEH and the fact that its "not supported anymore"

Is this a case again of ask before you read? You should know better. This question does not belong here because it is wasting time from other people.

No, its usual case of Thaddy sounding authoritative but being careful to not actually help at all.

Here, I will show you how it is done -

• https://www.freepascal.org/docs-html/ref/refch17.html
• https://wiki.freepascal.org/Exceptions

See how easy it is to include a link to something your correspondent clearly does not know about ? Give it a try some time.

I have added some text to the Wiki page, but at this stage, I see no reason to believe that the problem Pascal Dragon alerted us to is well documented in the official documentation, I quote -

On Windows with SEH using try … except-blocks without using the SysUtils unit is currently (from 3.2.0 on) not fully supported anymore, because the SEH implementation is missing some functions to allow the usage without that unit.

Davo

[Bart]

I have added some text to the Wiki page, but at this stage, I see no reason to believe that the problem Pascal Dragon alerted us to is well documented in the official documentation, I quote -

On Windows with SEH using try … except-blocks without using the SysUtils unit is currently (from 3.2.0 on) not fully supported anymore, because the SEH implementation is missing some functions to allow the usage without that unit.

And he goes on to say (when I asked wether this was documented):

No, because it's essentially a bug.

Bart

[PascalDragon]

I have added some text to the Wiki page, but at this stage, I see no reason to believe that the problem Pascal Dragon alerted us to is well documented in the official documentation, I quote -

On Windows with SEH using try … except-blocks without using the SysUtils unit is currently (from 3.2.0 on) not fully supported anymore, because the SEH implementation is missing some functions to allow the usage without that unit.

Because it's supposed to work. That it doesn't is a bug. Bugs are not going to be documented as part of the official documentation.

[dbannon]

Yes, PascalDragon, I see the argument, if its documented in the official documentation, its like saying its a behavior you can depend on, it will stay like that. And that is clearly wrong.

I will annotate the entry I put in the wiki to point out it is a bug and will, at some point in time be fixed at some level.

For most users, those who 'use sysutils' it is a not a problem anyway, adding SysUtils will not adversely affect too many apps in my opinion.

Davo