Segmentation fault when using HSolve with manual scheduling
Created by: subhacom
When autoschedule field of /sched/cj object is set to 0 (manual scheduling), and a cell has been read with readcell, a reset call causes a segmentation fault. The backtrace is: #1 (closed) 0x00007ffc0c9a6c5d in HSolveActive::getVm (this=0x3efa36e2eb1c432d, index=487) at HSolveInterface.cpp:39 (gdb) bt #0 0x00007ffc0c69a50a in std::vector<double, std::allocator<double> >::size (this=0x3efa36e2eb1c44b5) at /usr/include/c++/4.4/bits/stl_vector.h:533 #1 (closed) 0x00007ffc0c9a6c5d in HSolveActive::getVm (this=0x3efa36e2eb1c432d, index=487) at HSolveInterface.cpp:39 #2 (closed) 0x00007ffc0c9aedc7 in HSolveHub::getVm (e=...) at HSolveHub.cpp:671 #3 (closed) 0x00007ffc0c7859d5 in ValueFtype1<double>::get (this=0x1f14d50, e=..., f=0x2196a20, v=@0x7fff83e01d08) at ValueFtype.h:83 #4 (closed) 0x00007ffc0c6c36c7 in get<double> (e=..., f=0x2196a20, v=@0x7fff83e01d08) at ../basecode/setget.h:76 #5 (closed) 0x00007ffc0c6c34e2 in get<double> (e=..., f=..., v=@0x7fff83e01d08) at ../basecode/setget.h:98 #6 (closed) 0x00007ffc0c99b1ac in HSolvePassive::initialize (this=0x3b66850) at HSolvePassive.cpp:107 #7 (closed) 0x00007ffc0c99aa3e in HSolvePassive::setup (this=0x3b66850, seed=..., dt=2.5000000000000001e-05) at HSolvePassive.cpp:23 #8 (closed) 0x00007ffc0c9a3b7b in HSolveActive::setup (this=0x3b66850, seed=..., dt=2.5000000000000001e-05) at HSolveActiveSetup.cpp:25 #9 (closed) 0x00007ffc0c9a99cf in HSolve::setup (this=0x3b66850, integ=..., seed=..., dt=2.5000000000000001e-05) at HSolve.cpp:145 #10 (closed) 0x00007ffc0c9a98a6 in HSolve::setupFunc (c=0x3b48de0, seed=..., dt=2.5000000000000001e-05) at HSolve.cpp:136 #11 (closed) 0x00007ffc0c8a21a0 in void send2<Id, double>(Eref, Slot, Id, double) () from ./_moose.so #12 (closed) 0x00007ffc0c85dacd in Cell::setupSolver (this=0x1f19ad0, cell=..., seed=..., dt=2.5000000000000001e-05) at Cell.cpp:240 #13 (closed) 0x00007ffc0c85d1b7 in Cell::innerReinitFunc (this=0x1f19ad0, cell=..., p=0x22568b0) at Cell.cpp:182 #14 (closed) 0x00007ffc0c85cbad in Cell::reinitFunc (c=0x3b8fa50, p=0x22568b0) at Cell.cpp:156 #15 (closed) 0x00007ffc0c81927d in send1<ProcInfoBase*> (e=..., src=..., val=0x22568b0) at ../basecode/Send.h:54 #16 (closed) 0x00007ffc0c8bf333 in Tick::innerReinitFunc (this=0x2256b40, e=..., info=0x22568b0) at Tick.cpp:531 #17 (closed) 0x00007ffc0c8bef3b in Tick::reinit (c=0x3b92280, info=0x22568b0) at Tick.cpp:436 #18 (closed) 0x00007ffc0c81927d in send1<ProcInfoBase*> (e=..., src=..., val=0x22568b0) at ../basecode/Send.h:54 #19 (closed) 0x00007ffc0c8ba0e6 in ClockJob::reinitFuncLocal (this=0x2256880, e=...) at ClockJob.cpp:378 #20 (closed) 0x00007ffc0c8ba086 in ClockJob::reinitFunc (c=0x7fff83e024b0) at ClockJob.cpp:371 #21 (closed) 0x00007ffc0c761188 in set (e=..., f=0x21e60a0) at setget.cpp:23 #22 (closed) 0x00007ffc0c7612b4 in set (e=..., f=...) at setget.cpp:38 #23 (closed) 0x00007ffc0c7caf56 in Shell::reinit (c=0x39373d0) at Shell.cpp:2626 #24 (closed) 0x00007ffc0c74ab26 in send0 (e=..., src=...) at Send.cpp:27 #25 (closed) 0x00007ffc0c6905aa in pymoose::PyMooseContext::reset (this=0x2293900) at PyMooseContext.cpp:993 #26 (closed) 0x00007ffc0c43f6f7 in _wrap_PyMooseContext_reset () from ./_moose.so
Reported by: *anonymous
