modelview_test.py segfaults python

Debian's python2.7 and python3.2 do not segfault.

debian/rules ignores the value of the test runs with the debug interpreters. why? same problem which is hidden by the non-debug build?

<slangasek> fwiw if someone (ScottK?) considers not having pyside installable
            a problem and feels that it's better to have shiboken skipping the
            test suite and building with a known bug, I don't object [14:47]
<slangasek> I just don't think we should do that as non-users of the package

Does it also happen with the latest upstream release (1.1.2) ?

On Oct 27, 2012, at 11:33 AM, Didier Raboud wrote:

>Does it also happen with the latest upstream release (1.1.2) ?

Yes, in exactly the same way.

it segfaults for all pythons now, including the -dbg versions.

the problematic code part looks pretty broken:
...
       Py_DECREF((PyObject*)self);
    }
    //Python Object is not destroyed yet
    if (cppData && Shiboken::BindingManager::instance().hasWrapper(cppData)) {
        self->d->hasOwnership = false;
        // the cpp object instance was deleted
        delete[] self->d->cptr;
        self->d->cptr = 0;
    }
...

it decrefs self to zero and then dereferences members again, before a certain commit the comment:
// After this point the object can be death do not use the self pointer bellow
was below the decref instead of at the end of the function, so this code is very likely broken.

unfortunately this is not even the cause of the crash, it already crashes on the decref above, exchanging the order of the code segments does not fix it.

commenting the decref (introducing a memleak) fixes python2 but python 3 still fails:
  70 - sample_duck_punching (SEGFAULT)
 150 - sample_static_nonstatic_methods (SEGFAULT)

filed https://bugreports.qt-project.org/browse/PYSIDE-145 for the other failing tests
it also includes a hacky patch

also filed https://bugreports.qt-project.org/browse/PYSIDE-146 for the python multiarch path issue

I prepared a debdiff which fixes the build
the segfault is "fixed" by exchanging it by a memleak, ugly but I don't know how to fix it

This bug was fixed in the package shiboken - 1.1.2-2ubuntu1

---------------
shiboken (1.1.2-2ubuntu1) raring; urgency=low

  * python3.3-and-multiarch.patch:
    add python3.3 to list of python versions and deal with multiarch
    include paths
  * memleak-instead-crash.patch:
    to avoid crash on dereferencing object in tests introduce an intentional
    memleak until we have a proper fix (LP: #1070772)
  * static-override-fix.patch:
    fix broken static/non-static overloads in python3
  * update debian/shiboken-dbg.install and debian/rules makeshlibs override
    for new python abi suffixes not having "u"
 -- Julian Taylor <email address hidden> Sat, 23 Feb 2013 12:24:37 +0100