Your message dated Wed, 05 Mar 2008 21:17:04 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468998: fixed in python-fam 1.1.1-2.2
has caused the Debian Bug report #468998,
regarding python-fam: may use different memory API for a given memory block
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
468998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468998
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: python-fam
Severity: important
User: [EMAIL PROTECTED]
Usertags: goal-python2.5

The C API requires using the same memory API for a given memory block,
which will show up as a segfault, at least in python2.5. This code was
found by a search of all sources build-depending on python-dev, having
a PyObject_ function for allocation and a PyMem_ function for
deallocation in the same file.  This may be a real problem, or a false
positive.

The most common error seen is of the form:

  PyObject *
  new_wadobject(WadFrame *f, int count) {
    wadobject   *self;
    self = PyObject_NEW(wadobject, &WadObjectType);
    [...]
  }

  static void
  wadobject_dealloc(wadobject *self) {
    PyMem_DEL(self);
  }

This particular example can be fixed with replacing PyMem_DEL with
PyObject_Del.

For more information, see
http://docs.python.org/api/memory.html
http://docs.python.org/api/memoryExamples.html

Please set the severity of this report to "serious", if it is a real
problem, please close the report if it is a false positive.  Ask
the [EMAIL PROTECTED] ML for help. Archive of the
search results: http://ftp-master.debian.org/~he/affected-files.tar.gz



--- End Message ---
--- Begin Message ---
Source: python-fam
Source-Version: 1.1.1-2.2

We believe that the bug you reported is fixed in the latest version of
python-fam, which is due to be installed in the Debian FTP archive:

python-fam_1.1.1-2.2.diff.gz
  to pool/main/p/python-fam/python-fam_1.1.1-2.2.diff.gz
python-fam_1.1.1-2.2.dsc
  to pool/main/p/python-fam/python-fam_1.1.1-2.2.dsc
python-fam_1.1.1-2.2_i386.deb
  to pool/main/p/python-fam/python-fam_1.1.1-2.2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Viehmann <[EMAIL PROTECTED]> (supplier of updated python-fam package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


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

Format: 1.7
Date: Wed, 05 Mar 2008 20:09:23 +0100
Source: python-fam
Binary: python-fam
Architecture: source i386
Version: 1.1.1-2.2
Distribution: unstable
Urgency: low
Maintainer: Martin v. Loewis <[EMAIL PROTECTED]>
Changed-By: Thomas Viehmann <[EMAIL PROTECTED]>
Description: 
 python-fam - Python interface to FAM
Closes: 468998
Changes: 
 python-fam (1.1.1-2.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Add XS-Python-Source: all header.
   * Fix use of Python API for memory management. Closes: #468998
   * Fix debian/copyright.
   * Bump standards (no changes except the above).
Files: 
 7afd29a6b623a66be7916012806b6cf6 685 python optional python-fam_1.1.1-2.2.dsc
 4edf638f8c4b535c8f81febeab6a754d 2131 python optional 
python-fam_1.1.1-2.2.diff.gz
 7bed81befdf7874eb15147426f45ba2c 10828 python optional 
python-fam_1.1.1-2.2_i386.deb

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

iD8DBQFHzwp6riZpaaIa1PkRAoT0AKDZFP5j5d81XDl8/Vav3IVGMoTt5QCfZq1h
3eMOb1VGDu/AOUkVSmA9/EY=
=YTio
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to