Control: reopen -1 Control: notfixed -1 3.3.8-3 Control: tags -1 moreinfo ----- Forwarded message from Nikos Mavrogiannopoulos <[email protected]> ----- Date: Mon, 13 Oct 2014 19:10:54 +0200 From: Nikos Mavrogiannopoulos <[email protected]> To: [email protected] Subject: Bug#760476: fixed in gnutls28 3.3.8-3 Message-ID: <[email protected]> X-Spam-Report: (-5.7 / 8.0 requ) AWL=1.230,BAYES_00=-1.9,RCVD_IN_DNSWL_HI=-5,T_DKIM_INVALID=0.01,T_RP_MATCHES_RCVD=-0.01 autolearn=ham
On Sat, 11 Oct 2014 15:20:45 +0000 Andreas Metzler <[email protected]> wrote: > Source: gnutls28 > Source-Version: 3.3.8-3 > We believe that the bug you reported is fixed in the latest version of > gnutls28, which is due to be installed in the Debian FTP archive. Sorry, I misread the strace, and while the change done isn't bad is not relevant to the issue. I though getrusage failed, but the issue seems to be at: read(3, 0x7fffe61990b0, 16) = -1 EINVAL (Invalid argument) rather than getrusage(). The full strace could show which descriptor is 3, but my guess would be that it is /dev/urandom. Given that the size read 16 is sufficient to the stack variables I could speculate that someone closed the descriptor? In any case if possible, please provide the following: 1. The full strace to see what happens to fd 3 2. A valgrind debugging output 3. output when the environment variable GNUTLS_DEBUG_LEVEL=3 Let's hope that all of these types of errors will disappear when getrandom() is available. regards, Nikos ----- End forwarded message ----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
