[6.30 X64 C-Backend] OnErrorCall()

[GPI]

Code: Select all

  Procedure ErrorHandler()
    MessageRequester("OnError Test", "Der folgende Fehler trat auf: " + ErrorMessage())
  EndProcedure

  MessageRequester("OnError Test", "Test starten")

  OnErrorCall(@ErrorHandler())
  PokeS(10, "Hello World") ; verursacht einen #PB_OnError_InvalidMemory Fehler
  
  MessageRequester("OnError Test", "Dies sollte niemals angezeigt werden")

Simple Example from the Manual.
it crashes before ErrorHandle ist called on X64-C-Backend without any message.

Works without problems with X86-C-Backend.

[User_Russian]

This bug is many years old viewtopic.php?t=83498

[escape75]

Seems to work on 6.21 with debugger disabled ...

[GPI]

It seems, that the Debugger itself can't catch any crashes.

[Little John]

it crashes before ErrorHandle ist called on X64-C-Backend without any message.

Confirmed (with Debugger disabled).
Works also without problems when using the x64 ASM-backend.

[User_Russian]

Works also without problems when using the x64 ASM-backend.

Doesn't work with C backend.

[ChrisR]

It seems to work well here on Win11 x64, without the debugger and with both x86/x64 ASM and C compilers (optimized or not).

Code: Select all

CompilerIf #PB_Compiler_Debugger = #False
  OnErrorCall(@ErrorHandler())
CompilerEndIf

[Little John]

Works also without problems when using the x64 ASM-backend.

Doesn't work with C backend.

That was was written here before. With C backend x64, to be precise.
So what

[ChrisR]

It seems to work well here on Win11 x64, without the debugger and with both x86/x64 ASM and C compilers (optimized or not).

Code: Select all

CompilerIf #PB_Compiler_Debugger = #False
  OnErrorCall(@ErrorHandler())
CompilerEndIf

Hmm, strange!, it seems to depend on the error, I get it here.
But using GPI's example, or with a division by 0, ErrorHandler() is not called with the C Backend and it does not crash, it should. No issues with the ASM compiler!