#1062 test-ug fails with segfault
Metadata
Property | Value |
---|---|
Reported by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Reported at | Apr 10, 2012 15:34 |
Type | Bug Report |
Version | 2.0 |
Operating System | Unspecified / All |
Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Last edited at | Apr 10, 2012 16:40 |
Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Closed at | Apr 10, 2012 16:40 |
Closed in version | Unknown |
Resolution | Not a bug |
Comment |
Description
On my machine the latest ug patch (geometry storage) leads to a segfault.
The backtrace is:
#0 0x0000000100000017 in ?? () #1 (closed) 0x00000000005faf8c in ~BasicGeometry (this=, __in_chrg=) at /home/christi/Uni/Dune/geometry/dune/geometry/genericgeometry/geometry.hh:386 #2 (closed) ~UGGridGeometry (this=0x7fffffffc5b0, __in_chrg=) at ../../../dune/grid/uggrid/uggridgeometry.hh:184 #3 (closed) ~Geometry (this=0x7fffffffc5b0, __in_chrg=) at ../../../dune/grid/common/geometry.hh:81 #4 (closed) assertNeighbor<Dune::UGGrid<2> > (g=...) at gridcheck.cc:389 #5 (closed) 0x000000000065f25e in gridcheck<Dune::UGGrid<2> > (g=...) at gridcheck.cc:841 #6 (closed) 0x00000000005de8c5 in generalTests (greenClosure=true) at test-ug.cc:180 #7 (closed) 0x000000000069afb3 in main (argc=1, argv=0x7fffffffe2b8) at test-ug.cc:244
Perhaps this is reproducable when using valgrind?!
Additionally I have added the lifetime-check to the UG test. But the segfault occurs earlier.