I found the documentation http://valgrind.org/docs/manual/quick-start.html 
but the example under "4. Interpreting Memcheck's output" is with  malloc 
whereas my output  is with free:

==9729== Invalid read of size 4
==9729==    at 0x40DD82D: stash_as_reply (get_in_tkt.c:321)
==9729==    by 0x40DDFDE: krb5_get_init_creds (get_in_tkt.c:1263)
==9729==    by 0x40DF3D2: krb5_get_init_creds_keytab (gic_keytab.c:108)
==9729==    by 0x80897FC: krb5_create_cache (xxx.c:1167)
==9729==    by 0x8050AD8: main (xxx.c:368)
==9729==  Address 0x45954c4 is 4 bytes inside a block of size 84 free'd
==9729==    at 0x4026BFA: free (in 
/usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==9729==    by 0x40E3790: krb5_free_creds (kfree.c:221)
==9729==    by 0x80897A8: krb5_create_cache (xxx.c:1160)
==9729==    by 0x8050AD8: main (xxx.c:368)

How do I interpret this ?

Thank you
Markus


"Markus Moeller" <[email protected]> wrote in message 
news:[email protected]...
> Hi,
>
> When I run valgrind I get sometimes messages like:
>
> Invalid write of size x
> or
> Invalid read of size x
>
> in  my logfile.  What do they mean ? What do I need to do to fix them ?
>
> Thank you
> Markus
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev 



------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to