On 11/01/2025 07:53, Adriaan van Os via fpc-pascal wrote:
Am 10.01.2025 um 15:43 schrieb Adriaan van Os via fpc-pascal:
But now I install a system.ErrorProc and run the same program. It
emits, instead of the EBusError, Runtime Error 214.
This puzzles me.
This is as designed, because the Er
Sven Barth via fpc-pascal wrote:
Am 10.01.2025 um 15:43 schrieb Adriaan van Os via fpc-pascal:
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
misali
Am 10.01.2025 um 15:43 schrieb Adriaan van Os via fpc-pascal:
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 goo
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
___
fpc-pascal mai
On 2025-01-10 15:43, Adriaan van Os via fpc-pascal wrote:
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 n
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 progr
