Re: 'make check' and Use of uninitialised value in Curl_rand_hex
Date: Wed, 25 Jul 2018 20:34:21 -0400
On Wed, Jul 25, 2018 at 12:32 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:
> On Tue, 24 Jul 2018, Jeffrey Walton wrote:
>> My apologies if this has been asked previously. Google is not what it used
>> to be and showed one relevant hit at
>> I'm running a 'make check' on the latest release tarball. I'm catching a
>> lot of Valgrind findings for use of uninitialised value in Curl_rand_hex.
>> My question is, how should I interpret the result?
> That sounds like a bug. What curl version is this and what TLS library do
> you build with?
I used 7.61.0.tar.gz and openssl-1.0.2.o.tar.gz.
After thinking about this a bit, this may be due to -march=native on a
Core i5 6th gen. It is also a 64-bit machine so -m64 is present, too.
(When I am not building for distribution I build for the native