Open wxmerkt opened 5 years ago
@VladimirIvan @christian-rauch The source of this bug is that the state space and simple setup aren't finalised ("setup") until the first call of Solve
. Thus, growing a roadmap before the first solve has been called (as in example_prm.py
) causes a segmentation fault. There are a few issues that prevent easy fixes:
(a) We moved to this in order to be able to set correct bounds for the problem. That was broken.
(b) Previously when we first created problems and solvers specifically, we could change the problem before calling specifyProblem
to the solver - which circumvented this issue. Now the standard way is to use loadSolver
which specifies the problem automatically.
(c) Calling setup manually after checking isSetup is also crashing :'(
(d) We cannot reset the state space without resetting the simple setup - which is resetting everything.
(d) We cannot reset the state space without resetting the simple setup - which is resetting everything.
Does this go away if you specify the same problem twice (conflict with (c)...)? I wouldn't mind if we have to reset the whole simple setup during this operation.
This is directly related to #445 and #444:
grow_roadmap
results in a segmentation fault.example_prm
setup()
hasn't been called. This can be checked withisSetup()
.Backtrace: