[BCP] Segfault in OsiClpSolverInterface::clone after fathoming a node in BCP
Andrea Trautsamwieser
andrea.trautsamwieser at boku.ac.at
Wed Jul 25 08:36:46 EDT 2012
Hello again,
unfortunately I still have the same problem. I did also check the mailing list for Bcp and found
two similar problems.
[BCP] Pricing and dynamic cut generation in BPC from May 2008
[Coin-bcpdiscuss] Both cut and variable generation
But none of the answers does help me. I also tried to use variable generation and cut generation in serial now, so I only generate vars if no cuts have been found. But I still have the same problem, that after fathoming a node in the search tree, a problem occurs in
OsiClpSolverInterface::clone(bool) const().
Does anybody have a clue to solve this?
Thanks,
Andrea
Hi,
I am using BCP already quite a while but only used variable generation so far. Now I implemented cuts to strengthen the LP relaxation. However, I obtain the following problem when fathoming a node.
LP: Forcibly fathoming node in branch().
LP: Deleting 648 columns from the matrix.
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff791ffd8 in OsiClpSolverInterface::OsiClpSolverInterface(OsiClpSolverInterface const&) () from /home/andi/Bcp-1.3.4/build/lib/libOsiClp.so.1
I first thought that my algorithmic cuts are including variables that have been deleted. However, if I customize the function "select_vars_to_delete" of BCP_lp_user to delete nothing the error still occurs.
Thanks a lot for your help.
With kind regards,
Andrea
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.coin-or.org/pipermail/bcp/attachments/20120725/69f2872a/attachment.html>
More information about the BCP
mailing list