-
Notifications
You must be signed in to change notification settings - Fork 577
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
TeuchosParameterList_ObjectBuilder_UnitTests segfaults with GCC 5.3.0 #831
Comments
That above commit comment:
basically says it all. We need to stop throwing from destructors and expecting things to be handle gracefully. Just because standard compilers are supposed to allow this and handle this correctly (i.e. if no exceptions are thrown from a destructor during stack unwind), does not mean that we should write tests that depend on such behavior. In any case, for now, I am going to just ifdef out these two tests for GCC 5.3.0 so that I can make progress. This will likely need to get fixed once and for all when we disallow exceptions to get thrown from destructors as part of #229. |
…rilinos#482) This is needed to get a full passing test suite for the Primary Tested CI build based on GCC 4.8.2 (see trilinos#482).
…rilinos#482) This is needed to get a full passing test suite for the Primary Tested CI build based on GCC 4.8.2 (see trilinos#482).
This should have been resolved with the merge commit 0acaa65. Closing as complete. |
… Mac OSX Issue trilinos#907 is similar to Issue trilinos#831 and the fix is the same. See the discussion in trilinos#831 for more details. Tests: standard checkin-test.sh tests run, but on a Mac, so there are many test failures. Tests should be run on a RHEL 6 machine with SEMS before merging PR.
CC: @trilinos/teuchos
Related to: #482, #449
Description:
The test
TeuchosParameterList_ObjectBuilder_UnitTests
segfaults with the SEMS-provided GCC 5.3.0 compiler. It produces output like:It appears that the problem is two unit tests:
depend on behavior when throwing exceptions from destructors.
Apparently this is not the first time this has been seen. These two tests were ifdefed out for GCC 4.8 compilers in the commit:
Well, apparently this is a problem for GCC 5.3 as well. It seems this may be a defect in the compiler. However, a similar defect appears to exist in some Clang compilers as well (see #449).
The GCC 5.3.0 compiler is being investigated as a way to provide a standard pre-push CI env across Linix and OSX machines using the SEMS env (see #158 and #482).
The text was updated successfully, but these errors were encountered: