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

Multiple Umpire instances caused by shared library #1444

Open
gunney1 opened this issue Oct 11, 2024 · 0 comments
Open

Multiple Umpire instances caused by shared library #1444

gunney1 opened this issue Oct 11, 2024 · 0 comments
Labels
bug Something isn't working Build system Issues related to Axom's build system Reviewed

Comments

@gunney1
Copy link
Contributor

gunney1 commented Oct 11, 2024

In MR #1271, we saw multiple Umpire instances causing a crash because a pointer from one instance is not recognized by the other. This was caused by the combo of static Umpire libs and shared Axom libs. When Umpire logging was enabled, we got 2 log files.

We got the tests to pass by changing our CI tests to build Umpire with shared libs. But we should address the root cause of multiple Umpire instances. Maybe a better link command or rearrangement of linker switches will fix?

In MR #1271, we added reproducer tests quest_initialize.*_reallocations. When Umpire is built with static libs and Axom with shared libs, these should crash. Similar tests in mint and sidre did not reproduce the crash, indicating something about the link command in quest.

Possibly related to issues #865 #270 and #29.

@gunney1 gunney1 added bug Something isn't working Build system Issues related to Axom's build system labels Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Build system Issues related to Axom's build system Reviewed
Projects
None yet
Development

No branches or pull requests

2 participants