Kay Hayen

This unfortunately will have to wait until the discussed onefile improvements for the general code case happened.

I am waiting for @Maxwell175 to do Nuitka-Python on macOS. On Linux we had similar issues, but we added a bunch of flags that help the linker to know what...

Having had a brief look at the CPython flags on macOS, can you try compiling with `CCFLAGS=-dynamic` as it might go away then, checking CPython, they do not have the...

I guess, trying out options that CPython doesn't use is all fine and dandy, but not of immediate interest right now. I welcome if somebody were to figure it out,...

Nuitka is not very shy with private CPython APIs, that I can tell you. But so far, 3.10 is not yet fully supported, so this is in the far future....

I managed to verify that `libbacktrace` in fact claims to have found "dwarf" information. This is the case with `CCLFAGS="-gdwarf" LDFLAGS="-gdwarf` and without, not sure if it really read anything...

Ok, I think this got removed, the only instance of a call to `unw_get_proc_name` has been commented out. This has been done in commit 4ce5fd2 or on closer inspection, a...

Activating the traces, I am getting what I want, traced: ``` impl___main__$$$function__8_Proc2 0x5575bbcff150 CALL_FUNCTION_WITH_SINGLE_ARG 0x5575bbd41800 impl___main__$$$function__6_Proc0 0x5575bbd01d60 CALL_FUNCTION_WITH_SINGLE_ARG 0x5575bbd41800 impl___main__$$$function__4_pystones 0x5575bbcfbff0 CALL_FUNCTION_WITH_SINGLE_ARG 0x5575bbd41800 impl___main__$$$function__3_main 0x5575bbd050c0 CALL_FUNCTION_WITH_SINGLE_ARG 0x5575bbd41800 modulecode___main__ 0x5575bbd06b50 _EXECUTE_EMBEDDED_MODULE...

It seems it writes a table of code object identifiers at the end, probably something similar would be needed for native function names too.

Ok, when I did that, I found it never recorded what I was having on the stack. It seems to have some severe regressions for mixing C code and Python...