There was a recent fix for a bug in 3.13.0 "--xml-socket doesn't work":
https://bugs.kde.org/show_bug.cgi?id=382998
How does the valgrind project make a decision about releasing a bug fix version?
The number, nature, severity, and impact of the bugs;
the intrusiveness of the fixes, and the
On Tue, Aug 8, 2017 at 2:02 PM, John Reiser wrote:
> There was a recent fix for a bug in 3.13.0 "--xml-socket doesn't work":
>>
>> https://bugs.kde.org/show_bug.cgi?id=382998
>>
>
> How does the valgrind project make a decision about releasing a bug fix
>> version?
>>
>
>
There was a recent fix for a bug in 3.13.0 "--xml-socket doesn't work":
https://bugs.kde.org/show_bug.cgi?id=382998
This bug prevents using valgrind with Qt Creator on macOS 10.12. It's a
showstopper for some because we can't downgrade to 3.12.0 (it doesn't work
on macOS 10.12). (See