El 11/3/24 a les 11:38, Elmar Haneke via fpc-pascal ha escrit:
Presumably the problem is caused by calling your function from a
different thread.
Perhaps it is a solution to put the SerOpen in a thread created by FPC
and signal that thread from your dot-net-called function.
Nope, I tried,
When compiling for aarch64 with fpc 3.3.1 on macOS 14.2, I notice some new entries in the Mach-O
symbol table of the produced executable, e.g. apart from
SegmentName = __DATA_CONST
SectionName = __const
SymbolName = _VMT_$SYSTEM_$$_TOBJECT
n_type = 15
there is no
Presumably the problem is caused by calling your function from a
different thread.
Perhaps it is a solution to put the SerOpen in a thread created by FPC
and signal that thread from your dot-net-called function.
Am 09.03.24 um 16:24 schrieb Luca Olivetti via fpc-pascal:
I'm writing a dll tha
