Your message dated Mon,  3 Mar 2008 12:30:54 +0100 (CET)
with message-id <[EMAIL PROTECTED]>
and subject line false positive
has caused the Debian Bug report #468969,
regarding gdal: 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]

Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gdal
Severity: important
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

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) {

This particular example can be fixed with replacing PyMem_DEL with

For more information, see

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:

--- End Message ---
--- Begin Message ---

this bug seems to be a false positive on an #ifdef'ed backwards  
compatibility definition in a swig-generated file.

Kind regards

Thomas Viehmann,

--- End Message ---
Pkg-grass-devel mailing list

Reply via email to