Your message dated Fri, 07 Mar 2008 10:02:08 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468993: fixed in python-cdb 0.32-5.3
has caused the Debian Bug report #468993,
regarding python-cdb: 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.)
--
468993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468993
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: python-cdb
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-cdb
Source-Version: 0.32-5.3
We believe that the bug you reported is fixed in the latest version of
python-cdb, which is due to be installed in the Debian FTP archive:
python-cdb_0.32-5.3.diff.gz
to pool/contrib/p/python-cdb/python-cdb_0.32-5.3.diff.gz
python-cdb_0.32-5.3.dsc
to pool/contrib/p/python-cdb/python-cdb_0.32-5.3.dsc
python-cdb_0.32-5.3_i386.deb
to pool/contrib/p/python-cdb/python-cdb_0.32-5.3_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-cdb 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: Tue, 04 Mar 2008 22:41:01 +0100
Source: python-cdb
Binary: python-cdb
Architecture: source i386
Version: 0.32-5.3
Distribution: unstable
Urgency: low
Maintainer: Adam D. McKenna <[EMAIL PROTECTED]>
Changed-By: Thomas Viehmann <[EMAIL PROTECTED]>
Description:
python-cdb - Python CDB (constant database) library
Closes: 468993
Changes:
python-cdb (0.32-5.3) unstable; urgency=low
.
* NMU
* Fix memory allocations (Closes: #468993)
Files:
eeffc6b7b72d4ce900eed9f153c4fe10 626 contrib/python optional
python-cdb_0.32-5.3.dsc
5c36e93f391970d2781fc8b549624bfe 1866 contrib/python optional
python-cdb_0.32-5.3.diff.gz
0c83455b0a54ac3635ad07a22739a657 18430 contrib/python optional
python-cdb_0.32-5.3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH0Hj0riZpaaIa1PkRAmLbAKDdE6Lmn7z88JkSZddytjTZWJbq8wCgjHP/
PE4qEQYzoTPdQVjyxC6AMR8=
=DNWX
-----END PGP SIGNATURE-----
--- End Message ---
