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