|
From: Jeroen N. W. <jn...@xs...> - 2005-05-07 17:08:26
|
Nicholas wrote: > On Thu, 5 May 2005, Jeroen N. Witmond wrote: > >> memcheck/tests/x86/scalar fails because >> - line numbers do not match. I removed one line from the source (see >> previous mails) but the line numbers are off by three. >> - the format of some stack trace lines has changed: "__libc_start_main >> (...libc...)" vs. "__libc_start_main (in /...libc...)". >> - One error is not reported: >> - Syscall param sigaction(act) points to unaddressable byte(s) >> - at 0x........: syscall (in /...libc...) >> - by 0x........: __libc_start_main (in /...libc...) >> - by 0x........: ... >> - Address 0x........ is not stack'd, malloc'd or (recently) free'd > > This one should be fixed now. > You are right. It is fixed in both valgrind 2.4.0, and valgrind 3.0.0, where I first found it. (Nowadays, I should not use the name svn when I mean 3.0.0; it could cause confusion :-) Jeroen. |