Re: [Valgrind-users] Insight as to why Valgrind shows memory leak for LAPACKE_dgbsv

[<pa...@fr...>]

----- Original Message -----
> This is the first time I've ever used Intel's MKL LAPACKE and
> Valgrind. Unfortunately, I get an error with something I have little
> to no experience with. I could use some advice on how to cure a
> potential memory leak. I'm using Intel's MKL library, so I highly
> assume this issue is my fault, but I'm not exactly sure what to look
> for or how to debug the issue.

Hi

I'm not familiar with LAPACKE.

Looking at your Valgrind traces, thay say that you have possible leaks. The most likely cause is that LAPACKE is using a memory manager. I don't know if you need to use LAPACKE_malloc and LAPACKE_free, or whether you need to call some finalization function to free the LAPACKE memory pool.

Source code can be instrumented for memory pools (see http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mempools) but I doubt that will be feasible with LAPACKE.

A+
Paul