Re: Valgrind-3.15.0.RC1 is available for testing

Hello,

I have made RC1 available on the Snap package store in the "edge"
channel, so it can be tested on systems that have snap support with
"snap install --classic --edge valgrind".

I have also run the tests on Ubuntu 19.04 amd64 with gcc 8.3.0,
binutils 2.32, glibc-2.29, linux 5.0.0 and gdb 8.2.90.20190311.

== 709 tests, 4 stderr failures, 0 stdout failures, 2 stderrB
failures, 18 stdoutB failures, 4 post failures ==
gdbserver_tests/hginfo                   (stdoutB)
gdbserver_tests/hgtls                    (stdoutB)
gdbserver_tests/mcblocklistsearch        (stderrB)
gdbserver_tests/mcbreak                  (stdoutB)
gdbserver_tests/mcclean_after_fork       (stdoutB)
gdbserver_tests/mcleak                   (stdoutB)
gdbserver_tests/mcmain_pic               (stdoutB)
gdbserver_tests/mcsignopass              (stdoutB)
gdbserver_tests/mcsigpass                (stdoutB)
gdbserver_tests/mcvabits                 (stdoutB)
gdbserver_tests/mcwatchpoints            (stdoutB)
gdbserver_tests/mssnapshot               (stdoutB)
gdbserver_tests/nlcontrolc               (stdoutB)
gdbserver_tests/nlgone_abrt              (stdoutB)
gdbserver_tests/nlgone_exit              (stdoutB)
gdbserver_tests/nlgone_return            (stdoutB)
gdbserver_tests/nlpasssigalrm            (stdoutB)
gdbserver_tests/nlsigvgdb                (stdoutB)
gdbserver_tests/nlvgdbsigqueue           (stdoutB)

These all fail due to a minor change in the gdb output format as
described on https://bugs.kde.org/show_bug.cgi?id=406357


gdbserver_tests/mcinfcallWSRU            (stderr)
gdbserver_tests/mcinfcallWSRU            (stderrB)

This test fails to complete. I killed it after about 3 hours. The same
test from 3.14.0 completed on this setup.


none/tests/amd64-linux/map_32bits        (stderr)

Diff is:

--- map_32bits.stderr.exp       2019-04-08 09:20:28.000000000 +0100
+++ map_32bits.stderr.out       2019-04-09 14:29:28.408169636 +0100
@@ -1,3 +1 @@
-first mmap : 0x........
-last mmap ok: 0x........
-retry mmap ok: 0x........
+first mmap: Cannot allocate memory


exp-sgcheck/tests/stackerr               (stderr)

The __v*printf_internal part can be filtered, but I don't know what
the other part of the diff means:

--- stackerr.stderr.exp-glibc28-amd64   2019-04-08 09:20:27.000000000 +0100
+++ stackerr.stderr.out 2019-04-09 14:25:34.679919272 +0100
@@ -17,11 +17,11 @@

 Invalid write of size 1
    at 0x........: _IO_default_xsputn (in /...libc...)
-   by 0x........: ...
-   by 0x........: ...
+   by 0x........: __vfprintf_internal (vfprintf-internal.c:1644)
+   by 0x........: __vsprintf_internal (iovsprintf.c:95)
  Address 0x........ expected vs actual:
  Expected: stack array "buf" of size 8 in frame 4 back from here
- Actual:   unknown
+ Actual:   stack array "beforebuf" of size 8 in frame 4 back from here
  Actual:   is 0 after Expected


memcheck/tests/overlap                   (stderr)
cachegrind/tests/ann1                    (post)
cachegrind/tests/ann2                    (post)
callgrind/tests/ann1                     (post)
callgrind/tests/ann2                     (post)

These results are the same as reported by Carl and Mark:

Cheers,

Roger

On Mon, 8 Apr 2019 at 10:11, Julian Seward <[email protected]> wrote:
>
>
> Greetings.
>
> A first release candidate for 3.15.0 is available at
> https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC1.tar.bz2
> (md5 = 56d9f5e25615d48110da0aa5764d481e)
>
> Please give it a try on platforms that are important for you.  If no serious
> issues are reported, the 3.15.0 final release will happen on 12 April, that
> is, this coming Friday.
>
> J
>
>
> _______________________________________________
> Valgrind-developers mailing list
> Valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers