Custom Query (545 matches)

Valgrind report an error on the following code:

    ListPath<ListDigraph> p,q;
    p.addBack(a);
    q=p;

The problem seems to be that q=p tries to copy bitwise instead of using the template ListPath<>::operator=() implementation.

Implementing a non-template version solves the problem, but I don't understand why the template version is used.

I fear that this issue may affect other Path structures, or even other tools, too.

A user reported obvious memory leak when solving many MIP problem with a fresh CplexMip instance for each. In addition valgrind report the following on CplexMip:

==10084== Conditional jump or move depends on uninitialised value(s)
==10084==    at 0x8104C32: lemon::CplexEnv::~CplexEnv() (cplex.cc:66)
==10084==    by 0x81051C8: lemon::CplexBase::~CplexBase() (cplex.cc:94)
==10084==    by 0x8108C8E: lemon::CplexMip::~CplexMip() (cplex.cc:880)

The reason is that the constructor of CplexEnv does not initialize the target of the _cnt pointer when it is allocated.

CPLEX libraries and include files are at different placed based on the hardware, the OS, the compiler and the CPLEX version in use. Therefore all the paths must be passed to CMAKE by hand. A more sophisticated discovery method would make this much easier.