[Scip] Adding new constraints after solving the problem

[Timo Berthold]

Hi Rostislav,

> either by calling the next
> SCIPfreeTransform() or by calling the next SCIPfreeTransform()
I do not really see the either..or. ;-)

Anyhow, as a first attempt, have you tried compiling SCIP in debug mode (
make OPT=dbg) and running your program in a debugger, like, e.g., gdb?
Maybe an assert comes up beforehand that points a way to your problem.
if this is the case, you might post the assert, including the backtrace
(function call stack) and eventually values that are part of the failed
assert (e.g. when the assert says that two values should be equal, it can
be helpful to know which values they actually have in case of failure).

For debugging codes that use SCIP, also see
http://scip.zib.de/doc/html/DEBUG.shtml

If this does not help, the next step would be to run your code with
valgrind to detect the faulty memory access.

Best
Timo



> Dear SCIP community,
> I have the following problem - maybe did someone of you solved something
> similar:
> I would like to solve the instance by SCIPsolve(), then call
> SCIPfreeTransform() add new constraints and finally repeat the described
> process again until no more constraints are needed. All works fine if I
> do not add additional constraints during the solving process (e.g. in an
> event handler). But if I do so, the program falls with unauthorized
> memory access (SIGSEGV) (core dumped) either by calling the next
> SCIPfreeTransform() or by calling the next SCIPfreeTransform(). Am I
> doing something wrong? I add the constraints in the event handler in the
> same way as by defining of the origin problem - is it correct so?
> Thank you for your response.
> Best regards.
> Rostislav Stanek
> _______________________________________________
> Scip mailing list
> Scip at zib.de
> http://listserv.zib.de/mailman/listinfo/scip
>