Re: [Valgrind-users] Valgrind crash in check_mem_is_defined_asciiz?

[Julian S. <js...@ac...>]

On Monday 25 February 2008 14:16, Dan Kegel wrote:
> On Mon, Feb 25, 2008 at 5:10 AM, Dan Kegel <da...@ke...> wrote:
> >  http://sources.redhat.com/ml/libc-hacker/2005-11/msg00015.html
> >  and/or a moment's reflection
> >  suggests that touch x is an easier testcase than the one I found.
>
> Hrmph.  Without the patch,
>   valgrind touch x
> fails with a normal valgrind error, not a crash:
> ==6938== Syscall param utimensat(filename) points to unaddressable byte(s)
> ==6938==    at 0x40007F2: (within /lib/ld-2.6.1.so)
> ==6938==    by 0x410F4B6: futimesat (in /lib/tls/i686/cmov/libc-2.6.1.so)
> ==6938==    by 0x804D60F: (within /bin/touch)
> ==6938==    by 0x80497E9: (within /bin/touch)
> ==6938==    by 0x405704F: (below main) (in
> /lib/tls/i686/cmov/libc-2.6.1.so) ==6938==  Address 0x0 is not stack'd,
> malloc'd or (recently) free'd

I'm confused.  What does your PRE(sys_utimensat) routine now look like?

J