Your message dated Wed, 5 Mar 2008 11:55:54 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#468984: plplot: may use different memory API for a
given memory block
has caused the Debian Bug report #468984,
regarding plplot: 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.)
--
468984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468984
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: plplot
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 ---
On Sun, Mar 02, 2008 at 05:23:16PM +0100, Matthias Klose wrote:
> Package: plplot
> 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.
This is a false positive. The python bindings in plplot are generated by
swig. Swig includes an #if statement to use PyMem_DEL for old versions
of python. Newer versions will use PyObject_Del as required by
python2.5.
Andrew
--- End Message ---
