[fpc-devel] -dTEST_WIN32_SEH
Sergei Gorelkin
sergei_gorelkin at mail.ru
Sun Apr 13 17:54:02 CEST 2014
13.04.2014 19:06, Martin Frb пишет:
> On 13/04/2014 16:02, Martin Frb wrote:
>> Sorry.
>>
>> But the below on hold.
>>
>> I just found the log at the issue. And it seems fpc_raise was called.
>>
>> My fault
>
> OK, I excuse it by being Sunday afternoon. reread. Definitely not called.
>
Since the new exception handling is compilant with "official way to do it", I'd expect the debugger
to be notified about exception by Windows directly. But I have no idea about how gdb is compatible
with that. Maybe it must be configured in certain way.
Anyway, the exception information including its original address is still available when control is
passed to __FPC_except_handler. This handler is called twice, first time it initiates unwinding and
the second time restores the stack and jumps to code of "except" block.
Regards,
Sergei
More information about the fpc-devel
mailing list