Matias Vara <matiasev...@gmail.com> schrieb am Mi., 25. Juli 2018, 12:55:
> > El mar., 24 jul. 2018 a las 13:57, Sven Barth via fpc-pascal (< > fpc-pascal@lists.freepascal.org>) escribió: > >> Matias Vara <matiasev...@gmail.com> schrieb am Di., 24. Juli 2018, 11:04: >> >>> Hello, >>> >>> I am writing my own __FPC_specific_handler() but I can't figure out when >>> this function is registered. I guess this function is registered to the OS >>> to be invoked when an exception happens. In the assembler code I have >>> something like: >>> >>> .seh_handler __FPC_specific_handler,@unwind >>> >>> But I am puzzled by "@unwind". How is __FPC_specific_handler() invoked >>> >> >> To understand the .seh_*-pseudo instructions it's probably best to look >> at their initial check-in in the GNU assembler: >> https://sourceware.org/ml/binutils/2009-08/msg00193.html >> >> The handler function is invoked by Windows when an exception happens >> inside the code that is governed by the surrounding (implicit) >> .seh_(end)proc directives. >> >> Why are you writing your own handler? >> >> > Thanks for the answer, I am trying to make work the exceptions handling in > Toro kernel. Currently Toro is based on Win64 rtl. I think I will give up > with the Win64 RTL and move to a simpler RTL. > I think I suggested some time ago already that you should use the embedded targets for writing a kernel. That's what they're there for after all. Regards, Sven
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal