Leaderboard

A follow-up to this advice: After correcting the array error, I tested by reverting to the faulty version and enabling debugging information and symbols in the Release configuration. In this changed configuration, I was able to both create the error and debug it. So yes, that would have worked, and I could have saved a lot of time. Thank you.

Added to LLVM sort library it seems. https://www.nature.com/articles/s41586-023-06004-9 https://github.com/deepmind/alphadev -Tee-

So, if you're in USA get $100k/yr, what real income is?

Uninstall them. If that works, then reinstall one at a time until you know which one is the problem. From there, you're going to have to figure out why it won't run on ARM in a VM, which I would assume is not supported by any of them to begin with.

@James Steel let's try a new tip... if the bug is cause by a IDE settings, let's try create a new user for this IDE the RAD allow that you use many "user" in your desktop, then just use a command-line to execute this command> ... << your path where is RAD >> \bin\BDS.exe -r newusername <--- "-R" --> newusername = any name never used yet! ex.: c:\rad11\bin\bds.exe -r HelloWorldUser this way, will be create a new "environment" tottally fresh (none components, none addons) like the "first time" ok! in Registry, will be stored a new key em HCU\Software\Embarcadero\... HelloWorldUser key -> you can delete or not if desire use it another times! if ok, then, now you can create a shortcut for use it , else... let's try another tip: all RAD store your settings in c:\users\<<windows user name>>\AppData\Roamming\Embarcadero\BDS\<<nn.nn version>> then, do the backup and delete this folder << nn.nn version >> run you IDE and see if help you if nothing help, then, I think that the way is "re-install it" using a clean-install!!!

It's a good thing we have lawyers. Otherwise I would understand everything

I am way ahead of you. But I need to find those gems in the code I have taken over, before I can change them. The error in this post caused me to find one of them - and to discover that range check was disabled - so I consider my time well spent.

Did you restart Delphi, as per my reply?

RTTI had (and possibly still has) issues with thread safety when acquiring and releasing pool token. Unless you are using Windows application with dynamically loaded packages, the best option to avoid those issues is to call TRttiContext.KeepContext; in initialization section of some base unit and TRttiContext.DropContext; in finalization section. This will create pool token and keep it alive during lifetime of you application, avoiding thread safety issues, and it will also speed up RTTI operations.

Just to wrap this up: As @mvanrijnen (Thanks!) suggested in the end it was a missing dll or at least two of them. The debug file actually helped. If you know how, it is quite simple: In the section [Server.Logging] you uncomment the row that begins with Filename. And set the path you desire. You can actually write manually to that log with TEMSEndPointEnvironment.Instance.LogMessage('test'); Unit EMS.ResourceAPI is needed in the uses clause.

No (plus, that would require changing and recompiling the code, in which case you may as well just take out the offending code to begin with). But, you can accomplish something similar using breakpoints instead. Put a breakpoint at the beginning of the function, go into its properties, and disable the 'Break' option, and enable the 'Ignore subsequent exceptions' option. Then, put another breakpoint at the end of the function, go into its properties, and disable the 'Break' option, and enable the 'Handle subsequent exceptions' option.