|
From: Bart V. A. <bva...@ac...> - 2011-12-17 15:34:40
|
On Thu, Dec 15, 2011 at 9:51 AM, Philippe Waroquiers <
phi...@sk...> wrote:
> valgrind revision: 12308
> VEX revision: 2233
> C compiler: gcc (GCC) 4.6.2 20111027 (Red Hat 4.6.2-1)
> Assembler: GNU assembler version 2.21.53.0.1-3.fc16 20110716
> C library: GNU C Library development release version 2.14.90
> uname -mrs: Linux 3.1.0-0.rc9.git0.2.fc16.kh.ppc64 ppc64
> Vendor version: Fedora release 16 (Verne)
>
> Nightly build on gcc110 ( Fedora release 16 (Verne), ppc64 )
> Started at 2011-12-14 20:00:09 PST
> Ended at 2011-12-15 00:49:27 PST
> Results unchanged from 24 hours ago
>
Hello Maynard,
Had you already noticed this ppc-specific regression test failure ?
=================================================
./valgrind-new/memcheck/tests/ppc32/power_ISA2_05.stderr.diff
=================================================
--- power_ISA2_05.stderr.exp 2011-12-14 22:23:43.381000388 -0800
+++ power_ISA2_05.stderr.out 2011-12-14 22:28:50.539000388 -0800
@@ -1,4 +1,19 @@
+Invalid read of size 4
+ at 0x........: test_lfiwax (power_ISA2_05.c:54)
+ by 0x........: main (power_ISA2_05.c:204)
+ Address 0x........ is not stack'd, malloc'd or (recently) free'd
+
+
+Process terminating with default action of signal 11 (SIGSEGV)
+ Access not within mapped region at address 0x........
+ at 0x........: test_lfiwax (power_ISA2_05.c:54)
+ by 0x........: main (power_ISA2_05.c:204)
+ If you believe this happened as a result of a stack
+ overflow in your program's main thread (unlikely but
+ possible), you can try to increase the size of the
+ main thread stack using the --main-stacksize= flag.
+ The main thread stack size used in this run was ....
HEAP SUMMARY:
in use at exit: 0 bytes in 0 blocks
@@ -7,4 +22,4 @@
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
|