[Announce] Libgcrypt 1.4.0 (stable) released

Marcus Brinkmann marcus.brinkmann at ruhr-uni-bochum.de
Tue Dec 11 16:11:46 CET 2007


At Tue, 11 Dec 2007 14:53:37 +0200,
Ismail Dönmez <ismail at pardus.org.tr> wrote:
> 
> Monday 10 December 2007 21:01:06 tarihinde Werner Koch şunları yazmıştı:
> > Hello!
> >
> > We are pleased to announce the availability of Libgcrypt 1.4.0.  This is
> > the new stable version of Libgcrypt and upward compatible with the 1.2
> > series.
> 
> All tests fail here, already reported to bug-libgcrypt but can't find it on 
> the web so here it goes (this is same as Gentoo bug  #201917) :
> 
> Hi all,
> 
> I got all 16 tests crash with libgcrypt 1.4.0. It looks like 
> CFLAGS="-O2 -fomit-frame-pointer" causes the crash. First I thought it was a 
> compiler bug since I use gcc 4.3.0 trunk but valgrind reports the following 
> invalid read :
> 
> ==28359== Invalid read of size 1
> ==28359==    at 0x4037356: _gcry_detect_hw_features (hwfeatures.c:95)
> ==28359==  Address 0x4707b263 is not stack'd, malloc'd or (recently) free'd
> 
> All tests give the similar gdb backtrace :
> 
> (gdb) bt
> #0  0xb7f61356 in _gcry_detect_hw_features () at hwfeatures.c:95
> #1  0xb7f5ded8 in global_init () at global.c:81
> #2  0xb7f5e5b3 in _gcry_check_version (req_version=0x8048e54 "1.4.0") at 
> global.c:171
> #3  0xb7f5d06b in gcry_check_version (req_version=0x8048e54 "1.4.0") at 
> visibility.c:66
> #4  0x08048a45 in main (argc=Cannot access memory at address 0xd) hmac.c:161
> 
> Since hwfeatures.c line 95 refers to an inline asm block, I can't debug this 
> myself. Any help is appreciated.

Can you check with objdump -d which instruction in the asm it is that
gives the error?  (maybe send me the objdump -d output for the binary
matching the above log).

Thanks,
Marcus




More information about the Gcrypt-devel mailing list