Re: [Valgrind-users] phantom "new" at call leads to "definitely lost"

[Dan K. <da...@ke...>]

On Thu, May 30, 2013 at 9:15 AM, Alan Mazer <ala...@jp...> wrote:
> This type of error is occurring in a variety of places, always
> "definitely lost" memory at a function call.
>
> Anyone have any idea what I'm missing?  I've tried multiple compilers
> and a bazillion different options (on compiler and valgrind).  I'm stumped.

Have you looked at what the compiler is generating, or single-stepped
through that call?