I have an arm64 (aarch64) test program on MacOS that calls InterlockedExchangeAdd64 with a target variable that is not 8-byte aligned. Running the test program emits "EBusError: Bus error or misaligned data access".

So far so good.

But now I install a system.ErrorProc and run the same program. It emits, instead of the EBusError, Runtime Error 214.

This puzzles me.

Of course, I can add a bug report.

Regards,

Adriaan van Os

Is this really a bug? This depends on what you do in your ErrorProc implementation, doesn't it?

Tomas

Is this really a bug? This depends on what you do in your ErrorProc implementation, doesn't it?

Do a writeln the runtime number and break. But normally, a bus error, doesn't call into System.ErrorProc.

Regards,

Adriaan van Os

This is as designed, because the ErrorProc is what is used by the SysUtils unit to convert runtime errors to exceptions. If you want to implement your own handling, then store the original value of ErrorProc, assign your own handler, do your own handling and at the end call the saved ErrorProc.

Regards,
Sven

I don't want to handle the error, I want a meaningful error. And Runtime Error 214 "Collection overflow" is nonsense.

Regards,

Adriaan van Os

The sole purpose of overriding System.ErrorProc is to handle errors by yourself. If you don't want to handle a particular error, do as Sven said (call the original System.ErrorProc), and then whatever custom error handler that was there before will do its thing. In this case: the error handler that was installed by the SysUtils unit, which will raise an EBusError exception (which seems to be what you want).

Jonas