-
Notifications
You must be signed in to change notification settings - Fork 874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Double free on exit when design is saved (pyosys+gcc LTO only) #4535
Comments
I take it those are Arch versions. The crash is strange, we are crashing within the map erase call inside the |
These are Linux kernel versions, I forgot to specify that. |
Successfully reproduced in archlinux docker on up to date nixos. Hard to get debuginfod to work in docker though so I'll try on my manjaro laptop.
|
Manjaro laptop is a bit out of date and didn't reproduce.
|
To reproduce, it's sufficient to build with gcc, LTO, PYOSYS, and then run |
I can't put more time into this, but the core issue is that DesignPass and all_designs get destroyed in the "wrong" order. It seems resolving it isn't very easy, register.cc may have to be involved, as well as |
Version
Yosys 0.44 (git sha1 80ba43d, g++ 14.2.1 -march=x86-64 -mtune=generic -O2 -fno-plt -fexceptions -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -flto=auto -fPIC -O3
On which OS did this happen?
Linux
Reproduction Steps
Git clone
https://aur.archlinux.org/packages/yosys-git
Build and test
makepkg -s
The test also segfaults with the latest commit on main:
Yosys 0.44+9 (git sha1 4b9f45273, g++ 14.2.1 -march=x86-64 -mtune=generic -O2 -fno-plt -fexceptions -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -flto=auto -fPIC -O3)
I only run in to this issue on arch:
There are no issues when following the same steps on another PCs running manjaro 5.10 and manjaro 6.6.
Expected Behavior
No segfaults
Actual Behavior
yosys/tests/techmap/run-test.sh
segfaults. I have attached some debug infromation:GDB traceback of coredump
ldd
The text was updated successfully, but these errors were encountered: