[botan-devel] version 1.10 and Valgrind

Yuri Schaeffer yuri at nlnetlabs.nl
Thu Jan 28 04:06:09 EST 2016


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Our software uses SoftHSM which in turn links against libbotan. When I
try to run it in Valgrind, Valgrind will keep spewing this message as
fast as it can. Making debugging with this tool impossible for me.

In your 1.11.26 release notes I see:
* Checking const time assertions works with an unpatched valgrind now

Is this related to my issue and should I just upgrade or is it
something else?

libbotan 1.10 (I Think 1.10.10 according to my package manager)
valgrind-3.11.0
Linux 4.3.0-1-amd64

Regards,
Yuri

==23139== valgrind: Unrecognised instruction at address 0xb1628b2.
==23139==    at 0xB1628B2: ??? (in /usr/lib/libbotan-1.10.so.1.10)
==23139==    by 0xB2538AB: Botan::HMAC_RNG::reseed(unsigned long) (in
/usr/lib/libbotan-1.10.so
.1.10)
==23139==    by 0xB257D6D: Botan::ANSI_X931_RNG::reseed(unsigned long)
(in /usr/lib/libbotan-1.
10.so.1.10)
==23139==    by 0xB1B64F1:
Botan::Library_State::make_global_rng(Botan::Algorithm_Factory&, Bot
an::Mutex*) (in /usr/lib/libbotan-1.10.so.1.10)
==23139==    by 0xB1B7986: Botan::Library_State::global_rng() (in
/usr/lib/libbotan-1.10.so.1.1
0)
==23139==    by 0xAE1640B: SoftSession::SoftSession(unsigned long,
SoftSlot*, char*) (in /usr/l
ib/softhsm/libsofthsm.so)
==23139==    by 0xAE1573E: SoftHSMInternal::openSession(unsigned long,
unsigned long, void*, un
signed long (*)(unsigned long, unsigned long, void*), unsigned long*)
(in /usr/lib/softhsm/libs
ofthsm.so)
==23139==    by 0x446026: hsm_session_init (libhsm.c:599)
==23139==    by 0x44BAE1: hsm_attach (libhsm.c:3269)
==23139==    by 0x44981E: hsm_open2 (libhsm.c:2373)
==23139==    by 0x41D27A: lhsm_open (hsm.c:46)
==23139==    by 0x4140EF: engine_start (engine.c:1003)
==23139== Your program just tried to execute an instruction that Valgrin
d
==23139== did not recognise.  There are two possible reasons for this.
==23139== 1. Your program has a bug and erroneously jumped to a non-code
==23139==    location.  If you are running Memcheck and you just saw a
==23139==    warning about a bad jump, it's probably your program's faul
t.
==23139== 2. The instruction is legitimate but Valgrind doesn't handle i
t,
==23139==    i.e. it's Valgrind's fault.  If you think this is the case
or
==23139==    you are not sure, please let us know and we'll try to fix i
t.
==23139== Either way, Valgrind will now raise a SIGILL signal which will
==23139== probably kill your program.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlap2gEACgkQI3PTR4mhavhSbwCdH2Kv89xAOBuxiP4TUoPnPb5X
3g8An2EszPtlyDNmCPPE7qWJLU7oWYKd
=ztpk
-----END PGP SIGNATURE-----


More information about the botan-devel mailing list