On 03/25/2010 05:36 PM, Jacob Todd wrote:
On Thu, Mar 25, 2010 at 03:31:19PM -0300, Crístian Viana wrote:
either valgrind is doing something wrong or there's really some errors on
glibc.
I wouldn't doubt it.
There are always errors everywhere :P The problem is you shouldn't see
them since you're only interested in those in your own application.
Anyway, in this case, the "error" lies in that glibc recently started
using sse instructions to speed up some string operations on
intel-compatible CPUs, and Valgrind barks at those unless it has access
to the debugging symbols. On other distros this is no issue since they
make sure not to strip the libraries in question, or provide installable
*-debug packages. Gentoo doesn't provide this fine-grained debugging
support, and you have to build using splitdebug in FEATURES.
