-
Notifications
You must be signed in to change notification settings - Fork 11
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
Core dump when building on Ubuntu24.04 #32
Comments
This is probably another manifestation of epics-base/epics-base#514 Un-defining the C preprocessor macro |
I've run
I'm afraid I don't know how to undefine a macro in EPICS from epicscorelibs build process. Does that linked merged PR imply that this issue will be fixed in the future, with the next EPICS release? Is there anything I can do in the meantime to resolve this issue (asides from not using Ubunut-24)? |
hmm. I don't think that I have had to deal with this either, until now. Annoyingly, this is handled by |
Surprisingly, it looks like this may not be difficult. Apparently, for |
@AlexanderWells-diamond Could you test #33 ? |
No obvious luck when just dumping it into the existing CI run, see here. Neither any success when testing in my own Ubunutu-24.04 image - exactly the same error appears at exactly the same point. |
Please re-test. When attempting to test for With
then later many repetitions of |
We no longer see an abort, and the tests pass fine. Thank you for fixing this! |
#33 is merged. fyi. this is a workaround. The real fix will come with the next merge from epics-base into epicscorelibs. |
The PythonSoftIOC CI weekly run, which runs using "ubuntu-latest" and the master branches of all its various dependencies, is seeing a core dump in its latest runs.
The issue appears to be that "ubuntu-latest" is now "24.04", upgraded from "22.04". When building
epicscorelibs
on this system, it seems to cause a core dump when we first try and call into EPICS C code.I'm unfortunately not sure what the actual cause of the failure is. My guess is that the version of the C runtime has updated, but I would have expected building
epicscorelibs
on the system itself to not have an issue with that.I have a branch and PR where I have been investigating the issue here.
The text was updated successfully, but these errors were encountered: