Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Nuitka segfaults in ld call on aarch64
See original GitHub issuePython3.6.3 Linux 4.4 GCC 7.2.0 Aarch64
trying to compile a simple ‘hello world’ with:
pipenv run nuitka --show-scons --verbose print.py
segfaults as per in a call to ld as per:
https://gist.github.com/itdaniher/6343be4097dd35e78df5df06b3f88c8b
note that my compiler / linker chain is tested-working, built python and the kernel from source.
Issue Analytics
- State:
- Created 6 years ago
- Comments:20 (11 by maintainers)
Top Results From Across the Web
Nuitka segfaults in ld call on aarch64 · Issue #47 - GitHub
Any segfault of "ld" is its own. For all I know, the Debian tool chain works fine with Nuitka.
Read more >python package compiled with nuitka fails with segmentation ...
I'm using Nuitka python compiler for this. I've tried compiling separate modules of my application and it works fine, I can transparently replace...
Read more >ld crashes with stack overflow on AArch64/Darwin
Run Ghc LinkHs Stage0: _build/stage0/ghc/build/Main.o => _build/stage0/bin/ghc ld: warning: directory not found for option ...
Read more >nuitka Changelog - pyup.io
- Fix, must not expose module name objects to Python import hooks. Fixed in 1.0.8 already. - Fix, calls to bound methods of...
Read more >PyOxidizer - Release 0.23.0 Gregory Szorc
If an OxidizedFinder imports the pkg_resources module, register_pkg_resources() may be called automat- ically.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @kayhayen I have not yet been able to test your suggestion, but in the meantime I found a workaround. Just using clang instead of gcc “fixes” the problem. It must be that the ld/lld bug is triggered only when attempting to link object files generated by gcc.
I am happy with this at the moment. Thanks for you help!
Part of the 0.7 release.