Re: Is this a memory leak?

[John W. Eaton]

On 07/19/2016 02:42 AM, Susi Lehtola wrote:
> Some code in octave-gsl:
>
>      RowVector *y = new RowVector(gsl_sf_legendre_array_n (lmax));
>      double *yd = y->fortran_vec();
>      gsl_sf_legendre_array (GSL_SF_LEGENDRE_SPHARM, lmax, x, yd);
>
>      return octave_value_list(octave_value(*y));
>
> Is this a memory leak, since y is dynamically allocated but it's given
> as a dereferenced pointer to octave_value?

Yes, it is a leak.  You don't need to create the RowVector object with 
new.  The memory for RowVector, octave_value, and nearly all other 
objects in Octave is managed by reference counting.

> I tried running octave through valgrind, but I don't get any output..

What options did you use for valgrind?

jwe