On Sat, Oct 08, 2016 at 10:57:10PM -0000, Brad Parker wrote:
> Valgrind crashes when run on all applications linked to openssl.
>
> Valgrind reports:
>
> vex: the `impossible' happened:
> isZeroU
>
> valgrind: the 'impossible' happened:
> LibVEX called failure_exit().
>
>
> Upstream bug with fix is https://bugs.kde.org/show_bug.cgi?id=356393
This has been fixed upstream a very long time ago.
At this point it makes more sense to start testing and packaging
the new upstream release to see if it solves any outstanding issues
on Ubuntu. The beta is already out, final release will be October 20.
Please give it a try in configurations that are important for you, and
report any problems you have, either on this mailing list, or
(preferably) via our bug tracker at https://bugs.kde.org/enter_bug.cgi?product=valgrind
If nothing critical emerges, a final release will happen on
Thursday 20 October.
On Sat, Oct 08, 2016 at 10:57:10PM -0000, Brad Parker wrote: /bugs.kde. org/show_ bug.cgi? id=356393
> Valgrind crashes when run on all applications linked to openssl.
>
> Valgrind reports:
>
> vex: the `impossible' happened:
> isZeroU
>
> valgrind: the 'impossible' happened:
> LibVEX called failure_exit().
>
>
> Upstream bug with fix is https:/
This has been fixed upstream a very long time ago.
At this point it makes more sense to start testing and packaging
the new upstream release to see if it solves any outstanding issues
on Ubuntu. The beta is already out, final release will be October 20.
https:/ /sourceforge. net/p/valgrind/ mailman/ message/ 35405831/
A beta tarball for 3.12.0 is now available at www.valgrind. org/downloads/ valgrind- 3.12.0. BETA1.tar. bz2 861a23ed8531b18 29)
http://
(md5sum = cb91572285f0072
Please give it a try in configurations that are important for you, and /bugs.kde. org/enter_ bug.cgi? product= valgrind
report any problems you have, either on this mailing list, or
(preferably) via our bug tracker at
https:/
If nothing critical emerges, a final release will happen on
Thursday 20 October.