> Excellent, the svn version removes many violations. I still have a
> couple, though. Here are two samples which show up quite often:
>
> ==5789== Thread 1:
> ==5789== Invalid read of size 16
> ==5789==    at 0x303E27E164: __GI_strcmp (in /lib64/libc-2.11.1.so)

Try adding, to exp-ptrcheck/h_intercepts.c, the following line at the
obvious place:

STRCMP(VG_Z_LIBC_SONAME, __GI_strcmp)

> > AND 
>
> ==5789== Thread 4:
> ==5789== Invalid read of size 8
> ==5789==    at 0x303E324A99: __strncmp_ssse3 (in /lib64/libc-2.11.1.so)

Hmm, you'll need to create a STRNCMP template in h_intercepts.c do deal
with that.  You can just copy the relevant code from mc_replace_strmem.c.

If you do this and it works, please send the resulting diff.

J

------------------------------------------------------------------------------
Download Intel® 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