[Ipopt-tickets] Re: [Ipopt] #26: Segmentation fault with double free or corruption in DenseVector

[Ipopt]

#26: Segmentation fault with double free or corruption in DenseVector
--------------------------------+-------------------------------------------
  Reporter:  yong               |       Owner:  andreasw
      Type:  defect             |      Status:  assigned
  Priority:  high               |   Component:  Ipopt   
   Version:  3.2 (C++ Version)  |    Severity:  major   
Resolution:                     |    Keywords:          
--------------------------------+-------------------------------------------
Changes (by andreasw):

  * priority:  highest => high
  * status:  new => assigned
  * owner:  ipopt-team => andreasw

Comment:

 Hi there,

 We frequently check the correctness of memory management in Ipopt.  We use
 the free GNU tool 'valgrind' for this.  Since you also seem to use Linux,
 I suggest you run your application (compiled with debug code) with
 valgrind to see where the memory is being messed up; if it is in your code
 or in the Ipopt code.  (I'm assuming there that you are not using AMPL,
 but that you wrote your NLP formulation in some programming language and
 interfaced with the Ipopt library...?).

 If the first memory error shown by valgrind is indeed in the Ipopt code,
 please attach the valgrind output to this ticket.

 Thanks

 Andreas

-- 
Ticket URL: <https://projects.coin-or.org/Ipopt/ticket/26#comment:1>
Ipopt <http://projects.coin-or.org/Ipopt>
Interior-point optimizer for nonlinear programs.