Comment 32 for bug 6867

Message-ID: <20040719153535.GE14627@kiste>
Date: Mon, 19 Jul 2004 17:35:36 +0200
From: "Matthias Urlichs" <email address hidden>
To: Modestas Vainius <email address hidden>, <email address hidden>
Subject: Re: Bug#244827: libgcrypt7: more info

--9l24NVCWtSuIVIod
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

Modestas Vainius:
> The problem persists with libgcrypt7_1.1.90-9 and libgnutls10_1.0.4-3.

Thanks for the info.

> However, the bug is not in gcry_mpi_get_opaque(), but in _gcry_mpi_copy()

Thought so...

> gdb provides inaccurate backtrace when libgcrypt7 is compiled with -O2

Not really -- gcc just suppresses symbol names which aren't externally
reachable, and gdb then uses the sybols it does see...

> (gdb) p a->d
> $2 =3D (mpi_limb_t *) 0x10
>=20
*Grumble* I hate bugs like these.

> 1) Start slapd ( slapd -d0 -h "ldap:/// ldaps:///" ). Be sure TLS is
> enabled in slapd.conf
>=20
Actually, /etc/default/slapd. ;-)

> By the way, I was able to trigger the bug only with the script
> concurrenly running in two or more consoles, so it seems that the bug
> only occurs in a threaded environment.
>=20
Looks like a nicely impossible-to-find memory corruption bug. Happiness.
Did you try to reproduce it under Electric Fence?

--=20
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | <email address hidden>

--9l24NVCWtSuIVIod
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA++pH8+hUANcKr/kRAs37AJ9UE0u5v479E6QDj9uP1QYDgM+wewCfZHXA
6CIZF3bMgnqoI+EmWEoO4XQ=
=YHEg
-----END PGP SIGNATURE-----

--9l24NVCWtSuIVIod--