Hi Edscott,
In the worst case, these are small numerical errors resulting from the different compilations that are accumulating over the Newton iterations and over time. That's what the outputs suggest. In the far better case, memory is accessed out of bounds. Can you recompile things with debug options and see if you run into an assertion or segmentation fault? If not, can you run a memory checker like valgrind on your executables compiled with debug options? Kind regards Bernd ________________________________ Von: Dumux <[email protected]> im Auftrag von Ed Scott Wilson Garcia <[email protected]> Gesendet: Dienstag, 30. Januar 2018 21:26:36 An: DuMuX User Forum Betreff: [DuMuX] gcc7 issue Hi all, With both dumux-2.11 and 2.12 and gcc-6.3.1, we are solving a problem, but when we switch to gcc7, the problem no longer converges. It is the exact same problem. The only difference is the gcc version used. Would this be a dumux or dune issue? I'm attaching log files for the run for the same problem, one with gcc6 and the other with gcc7. Any pointers would be greatly appreciated. kind regards, Edscott
_______________________________________________ Dumux mailing list [email protected] https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
