Also, there is no symbol information (on MacOS). Is this because of the
separate .dSYM file ?
But if I call backtrace_symbols in stead of DUmp_Stack, I do get symbol names
Regards,
Adriaan van Os
main program
0 Test0x00011560
P$MBTESTBACKTRACE2_$$_
Karoly Balogh via fpc-devel wrote:
Hi,
On Fri, 4 Oct 2024, Adriaan van Os via fpc-devel wrote:
My question now is if there is a reason why FPC doesn't call backtrace (see
man backtrace) on Linux and Unix (including MacOS) platforms ?
It seems this is a relatively recent addition to libc, whi
Op 04/10/2024 om 17:44 schreef Karoly Balogh via fpc-devel:
Same applies to BSDs. We used to support earlier BSD version than where
this call existed. Not sure that is still true tho'.
FreeBSD is also a syscall port.
___
fpc-devel maillist - fpc-de
Hi,
On Fri, 4 Oct 2024, Adriaan van Os via fpc-devel wrote:
> My question now is if there is a reason why FPC doesn't call backtrace (see
> man backtrace) on Linux and Unix (including MacOS) platforms ?
It seems this is a relatively recent addition to libc, which means, after
2000. :)
I suppose
It looks like the FPC RTL function CaptureBacktrace uses a system call if
FPC_SYSTEM_HAS_CAPTUREBACKTRACE is true and a custom routine if it is false. The define
FPC_SYSTEM_HAS_CAPTUREBACKTRACE seems to be true for Windows with Structured Exception Handling
(FPC_USE_WIN64_SEH) where RtlCaptureSt
