Skip to content
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

_Unwind_GetDataRelBase() not implemented #146

Open
crisluengo opened this issue Mar 16, 2024 · 0 comments
Open

_Unwind_GetDataRelBase() not implemented #146

crisluengo opened this issue Mar 16, 2024 · 0 comments
Labels
bug component:building About building the project

Comments

@crisluengo
Copy link
Member

crisluengo commented Mar 16, 2024

Since recently, DIPlib compiled with GCC on an M1 macOS machine crashes whenever an exception is thrown outside the library (this happens both on my own iMac and my work MacBook Pro). It prints to the command line:

libunwind: _Unwind_GetDataRelBase - _Unwind_GetDataRelBase() not implemented

and terminates with SIGABRT. This can be reproduced by just running the tests. It happens both in debug and release modes. The Python bindings cause Python to abort when an error is generated.

I'm using GCC 13.2.0 installed through Homebrew, and Xcode 15.0.0. This didn't use to happen until recently (I've upgraded both Xcode and GCC!). It also does not happen when compiling with Clang, and is not observed on the CI runner (one of which is an Intel macOS machine compiling with an older Xcode Clang, another is an Intel Linux machine compiling with GCC).

The only related issue I've found online is this one: https://gromacs.bioexcel.eu/t/pressure-equilibration-on-mac-not-working/8314 -- not very helpful.

The unimplemented function, according to Linux documentation is an IA64 function, I wouldn't expect it to be called on an aarch64 platform. So I'm not surprised it's not implemented. But why is it being called?

I could not reproduce this issue with a simple project, I'm not sure which feature of DIPlib is causing this issue.


For now, if you happen to have this issue, the workaround is to build with Xcode Clang.

Another solution is to install GCC 12 (brew install gcc@12), then configure CMake to use gcc-12 and g++-12. This issue seems specific to GCC 13.

@crisluengo crisluengo added bug component:building About building the project labels Mar 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug component:building About building the project
Projects
None yet
Development

No branches or pull requests

1 participant