Any success running john with valgrind/eeyes in order to find out where the=
=20
sparc issue might reside? I would hate to drop sparc from the supported=20
archs, but if we don't do it in the next upload probably the latest=20
revision (which includes quite a number of bug fixes) will not make it into=
=20
sarge in time for release...
Regards
Javier
--8t9RHnE3ZwKMSgU+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
Message-ID: <email address hidden> 15?Q?Fern= E1ndez- Sanguino_ Pe=F1a? = <email address hidden>
Date: Tue, 30 Mar 2004 10:03:33 +0200
From: Javier =?iso-8859-
To: <email address hidden>
Subject: Any success testing malloc errors?
--8t9RHnE3ZwKMSgU+ Disposition: inline Transfer- Encoding: quoted-printable
Content-Type: text/plain; charset=iso-8859-15
Content-
Content-
Hi there,
Any success running john with valgrind/eeyes in order to find out where the=
=20
sparc issue might reside? I would hate to drop sparc from the supported=20
archs, but if we don't do it in the next upload probably the latest=20
revision (which includes quite a number of bug fixes) will not make it into=
=20
sarge in time for release...
Regards
Javier
--8t9RHnE3ZwKMSgU+ pgp-signature; name="signature .asc" Description: Digital signature Disposition: inline
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
ehJTrj0oRApmiAJ 48CBdncqnhwsA2l yBh5UZ4cnxZ0ACd FxP5 gmxX1uTQ=
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAaSnVi4s
xCaMb2rlR7jI46A
=ngGi
-----END PGP SIGNATURE-----
--8t9RHnE3ZwKMS gU+--