Solve gcc bugs on current develop branch
-
The one for instance met here in CI for two tests but only for gcc and in debug mode... Both in Fedora and Ubuntu, but not on macOS.
-
On macOS, test
TestSolidPoissonWithoutYoung
fails with an impressive error:
[0]PETSC ERROR: ------------------------------------------------------------------------
164: [0]PETSC ERROR: Caught signal number 10 BUS: Bus Error, possibly illegal memory access
164: [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
164: [0]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind and https://petsc.org/release/faq/
164: [0]PETSC ERROR: --------------------- Stack Frames ------------------------------------
164: [0]PETSC ERROR: No error traceback is available, the problem could be in the main program.
164: --------------------------------------------------------------------------
but in fact the issue is when an exception is thrown and the message for it is prepared; the call to std::source_location::current().file_name()
fails. I'm puzzled by this one: it does not manifest in any other exceptions???
And it's really related to file_name()
; function_name()
is ok...