Failure in checkpointing: stack smash on readVTKFile()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fluidity |
Incomplete
|
Medium
|
Jon Hill |
Bug Description
This bug causes Fluidity to crash upon reading in a checkpoint, and is absolutely repeatable. Checkpointing becomes unusable.
Operating systems / software:
- Fully-updated Ubuntu 11.04, 11.10, 12.04
- Stock Ubuntu versions of OpenMPI, PETSc, ParMetis, VTK, Python-Numpy, etc. (excepting Zoltan)
- Fluidity releases 4.1.6, 4.1.7.1, and trunk.
Conditions of error:
1) Defining environmental variables CFLAGS, CXXFLAGS, and FCFLAGS with -O2 or -O3
2) Compiling Fluidity with ./configure --enable-vtk --with-zoltan --enable-
3) Running test case water_collapse_2d
4) Editing finish_time in water_collapse_
5) Running fluidity -v 2 water_collapse_
Nature of error:
- Fluidity crashes upon trying to read in the checkpointed pressure vtu file.
- Traceback indicates point of failure readVTKFile() / vtk_get_sizes() / vtk_read_state()
(Log attached to bug entry)
Steps for bug work-around:
1) Remove optimisation flags (eg. -O2 or -O3) from enviromental variables CFLAGS, CXXFLAGS and FCFLAGS
2) make distclean
3) Re-run ./configure and recompile Fluidity
Suggested interim fix:
./configure informs users that the environmental variables CFLAGS, CXXFLAGS and FCFLAGS are picked up by configure. It should now also recommend removing -O/-O2/-O3 from these variables (and state why you should do so).
description: | updated |
description: | updated |
description: | updated |
Changed in fluidity: | |
assignee: | nobody → Jon Hill (jon-hill) |
status: | New → Confirmed |
importance: | Undecided → Medium |
Have you modified water_collapse.flml at all before step 3?
The reason I ask is because with this example there shouldn't be a water_collapse_ 17_checkpoint. flml (it should reach water_collapse_ 50_checkpoint before terminating producing no checkpoints before then).
Does the first run exit cleanly? Are any errors reported in fluidity.err-0?