Hi,
thanks for the quick reply. The submitted example is a close to minimal test case.
Command lines:
icc tstr.c -g -O2
...
valgrind ./a.out | & less
valgrind versio is 3.3.0, flags enabled by default are: -v --trace-children=yes --time-stamp=yes --error-limit=no --leak-check=full
--leak-resolution=high
best,
Andreas
Looks like this is a known limitation of valgrind. See http://valgrind.org/docs/manual/dist.news.html under Known Limitations:
- Memcheck is unusable with the Intel compiler suite version 11.1, when it generates code for SSE2-and-above capable targets. This is because of icc's use of highly optimised inlined strlen implementations. It causes Memcheck to report huge numbers of false errors even in simple programs. Helgrind and DRD may also have problems.
If you're using the compiler for 32-bit, you can use the -mia32 option to workaround this, but this option will likely impact your performance.
--------
Brandon Hewitt
Intel Developer Support
Tools Knowledge Base: http://software.intel.com/en-us/articles/tools
Software Product support info: http://www.intel.com/software/support
* Other names and brands may be claimed as the property of others.
