padlock + SIGSEGV
marcus.brinkmann at ruhr-uni-bochum.de
Sun Jan 27 14:35:16 CET 2008
At Sun, 27 Jan 2008 12:08:47 +0200,
Nikos Mavrogiannopoulos wrote:
> In some occasions I've noticed some segmentation fauls on padlock code. This
> was using the debian libldap + gnutls13 + libgcrypt 1.4.0.
> I'm trying to understand why this is happening, but I have no clue. Notice
> that the stack changes after entering the "asm volatile". To make it more
> interesting gnutls-cli compiled with gnutls13 and libgcrypt 1.4.0 works as
> expected. gnutls_global_init() is used in both cases so it shouldn't be
> initialization error. Any suggestions on why this might happen?
Can you test if this was fixed in the SVN repository by:
2008-01-21 Marcus Brinkmann <marcus at g10code.de>
* hwfeatures.c (detect_ia32_gnuc): Fix inline asm.
It seems to be the same bug as was reported before.
More information about the Gcrypt-devel