In our previous episode, Reinier Olislagers said:
> > Is it usefull to make DISABLE_WIN64_SEH a command line switch?
>
> >From my perspective: no, as it breaks using external dlls whose
> errors/exceptions incorrectly bubble up through to FPC.
>
> However, perhaps Sergei has another opinion...
P
On 9-3-2013 13:51, Florian Klaempfl wrote:
> Am 09.03.2013 08:49, schrieb Reinier Olislagers:
>> Sergei Gorelkin enabled Win64 SEH support in trunk r23732:
>>
>> * Make Win64 SEH support enabled by default. If necessary to disable,
>> compiler should be cycled with OPT=-dDISABLE_WIN64_SEH. Mantis #
Am 09.03.2013 08:49, schrieb Reinier Olislagers:
Sergei Gorelkin enabled Win64 SEH support in trunk r23732:
* Make Win64 SEH support enabled by default. If necessary to disable,
compiler should be cycled with OPT=-dDISABLE_WIN64_SEH. Mantis #24012.
Is it usefull to make DISABLE_WIN64_SEH a co
Am 09.03.2013 09:36 schrieb "Paul Ishenin" :
>
> 09.03.13, 15:49, Reinier Olislagers пишет:
>
>> Sergei Gorelkin enabled Win64 SEH support in trunk r23732:
>>
>> * Make Win64 SEH support enabled by default. If necessary to disable,
>> compiler should be cycled with OPT=-dDISABLE_WIN64_SEH. Mantis #
09.03.13, 15:49, Reinier Olislagers пишет:
Sergei Gorelkin enabled Win64 SEH support in trunk r23732:
* Make Win64 SEH support enabled by default. If necessary to disable,
compiler should be cycled with OPT=-dDISABLE_WIN64_SEH. Mantis #24012.
Does win32 SEH differs much from 64 bit version?
B
Sergei Gorelkin enabled Win64 SEH support in trunk r23732:
* Make Win64 SEH support enabled by default. If necessary to disable,
compiler should be cycled with OPT=-dDISABLE_WIN64_SEH. Mantis #24012.
Seems this fixes issues on Win64 with e.g. embedded Firebird dlls, and
I'm sure many other DLLs.