[Ipopt] [Coin-discuss] Trouble with C interface: glibc memory corruption error

[John Pye]

Hi all

Looks like my problem here was relating to a silly mistake where I had
set the number of optimisation variables 'n' to less than the number of
constraints 'm'. Perhaps there should be an assertion somewhere in the
IPOPT code to prevent this (or perhaps there already is, but I didn't
manage to turn it on :-)

Thanks all for the suggestions.

Cheers
JP

John Pye wrote:
> Andreas Waechter wrote:
>   
>> Hi John,
>>
>> My guess would be that there is wrong use of Ipopt's SmartPtr's.
>> Please read the section on SmartPtr in the Ipopt documentation carefully,
>>
>> http://www.coin-or.org/Ipopt/documentation/node57.html
>>
>> The main point is that if you create any of the Ipopt objects (which
>> inherit from ReferencedObject), you must use a SmartPtr to store the
>> object in when you get it from "new".
>>     
>
> But I'm using the C interface, right, so do I still need to pass
> SmartPtrs to CreateIpoptProblem?
>
> Cheers
> JP
>
> _______________________________________________
> Ipopt mailing list
> Ipopt at list.coin-or.org
> http://list.coin-or.org/mailman/listinfo/ipopt
>