[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted valgrind 1.9.6-1 (i386 source)



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

Format: 1.7
Date: Sat, 10 May 2003 18:53:36 +0000
Source: valgrind
Binary: valgrind
Architecture: source i386
Version: 1.9.6-1
Distribution: unstable
Urgency: low
Maintainer: Andrés Roldán <aroldan@fluidsignal.com>
Changed-By: Andrés Roldán <aroldan@fluidsignal.com>
Description: 
 valgrind   - A memory debugger for x86-linux
Changes: 
 valgrind (1.9.6-1) unstable; urgency=low
 .
   * New upstream version.
   * Removed the patch from Anders Gustafsson since it is already on the
     upstream source.
   * Added FAQ.txt to documentation (please read it).
   * Changed default suppresion to sarge.supp. I left woody.supp and
     potato.supp for compatibility.
   * Added a stolen-from-HEAD patch from Crispin Flowerday that closes all the
     opened file descriptors when the work is done.
   * Added a stolen-from-HEAD patch from Jeffrey Stedfast to avoid confussion
     when the number of the suppression callers is >= VG_N_SUPP_CALLERS.
   * Added a stolen-from-HEAD patch from Troels Walsted Hansen that allows reuse
     of the socket.
Files: 
 6b9072159375cce4872e4307a4c337c8 713 devel optional valgrind_1.9.6-1.dsc
 76459a412cb7a73085296f55db003bfc 852979 devel optional valgrind_1.9.6.orig.tar.gz
 6da478a2ded57dbb4e2ff734f2e120e4 9780 devel optional valgrind_1.9.6-1.diff.gz
 934279cfb068ef47ead9aff01c3bc4ea 784960 devel optional valgrind_1.9.6-1_i386.deb

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

iD8DBQE+xQ7S4IYBx2bmiZMRAnKmAJ93nWNvWz668ao13hmUWwxHZOxEzgCgjiHo
0ueyMkzT7ce2qjYqzPTI3Yg=
=Cr73
-----END PGP SIGNATURE-----


Accepted:
valgrind_1.9.6-1.diff.gz
  to pool/main/v/valgrind/valgrind_1.9.6-1.diff.gz
valgrind_1.9.6-1.dsc
  to pool/main/v/valgrind/valgrind_1.9.6-1.dsc
valgrind_1.9.6-1_i386.deb
  to pool/main/v/valgrind/valgrind_1.9.6-1_i386.deb
valgrind_1.9.6.orig.tar.gz
  to pool/main/v/valgrind/valgrind_1.9.6.orig.tar.gz



Reply to: