Re: Valgrind-3.15.0.RC2 is available for testing

Hello,

I tested RC2 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.

I get the same problems as before, less the ones that have been fixed.

If I retest with LTO enabled I get a new error:

helgrind/tests/tc09_bad_unlock           (stderr)

--- tc09_bad_unlock.stderr.exp  2019-04-11 08:48:32.000000000 +0100
+++ tc09_bad_unlock.stderr.out  2019-04-11 11:12:21.345129726 +0100
@@ -117,7 +117,6 @@
    by 0x........: nearly_main (tc09_bad_unlock.c:31)
    by 0x........: main (tc09_bad_unlock.c:49)
  Address 0x........ is on thread #x's stack
- in frame #x, created by nearly_main (tc09_bad_unlock.c:16)

Regards,

Roger


On Thu, 11 Apr 2019 at 09:56, Julian Seward <[email protected]> wrote:
>
>
> Thank you to everybody who tested RC1, sent reports and bug fixes.
>
> RC2 is now available at
> https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC2.tar.bz2
> (md5 = 672e065ec63ae127ee4439cd296fb142).  It contains fixes for
> five minor regression test failures, but nothing major.
>
> Unless any serious failures are reported in RC2, this is very likely
> to morph into the final 3.15.0 release.
>
> J
>
> > On 08/04/2019 11:11, Julian Seward wrote:
> >
> > 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