Re: [Valgrind-users] cachegrind on Darwin

[Nicholas N. <n.n...@gm...>]

On Wed, Jun 10, 2009 at 10:54 AM, Nicholas
Nethercote<n.n...@gm...> wrote:
>
> I was just looking at this.  It's a tricky case, lstat64_extended()
> has 4 arguments.  The first two are the same as lstat(), and are easy.
>  But the last two are pointers, xsecurity and xsecurity_size, and I'm
> having trouble working out how big are the buffers that they point to.
>
> I think xsecurity_size points to a word-sized buffer, and that the
> value in xsecurity_size is the size of xsecurity, and that
> xsecurity_size is updated with the number of bytes written
> (somewhere?) but I'm not completely sure.

I just discovered that stat_extended is already wrapped, so doing
lstat_extended from that should be easy.

Nick