Hugo Lima wrote:
> If your case is similar to that, dont worry at all, otherwise it´s a
> bug. Can you tell us the class and method name that is triggering
> this?
>
Like now I'm not able to debug or know witch part of code create the
problem since it's a third-part code. Can be because I "remove" PyQt4
from my site-packages and renamed PySide with its name? So I tried to
cheat it :)
Compiling pyside-shiboken with debug and tried inside gdb, I receive
this [1]
Don't know if help, but with my own software, I see that it abort too
and always into "QPoint" peace of code. If I modify it for use PySide
instead of PyQt4 it works.
Michele
[1]
#0 0xb77ac424 in __kernel_vsyscall ()
#1 0xb74738e0 in raise () from /lib/i686/cmov/libc.so.6
#2 0xb7476e15 in abort () from /lib/i686/cmov/libc.so.6
#3 0xb746cace in __assert_fail () from /lib/i686/cmov/libc.so.6
#4 0xb6da3e9a in registerTypeResolver (resolver=0x850db78) at
/home/devel/pyside/shiboken/libshiboken/typeresolver.cpp:75
#5 0xb6da4028 in TypeResolver (this=0x850db78, typeName=0xb711c8e0
"QPoint",
cppToPy=0xb7028ade
<Shiboken::ValueTypeConverter<QPoint>::toPython(void*)>,
pyToCpp=0xb7028a2a <void*
Shiboken::pythonToValueType<QPoint>(_object*)>, pyType=0xb7181ce0,
deleter=0xb702896c <void Shiboken::objectDeleter<QPoint>(void*)>) at
/home/devel/pyside/shiboken/libshiboken/typeresolver.cpp:88
#6 0xb7028ab0 in
Shiboken::TypeResolver::createValueTypeResolver<QPoint>
(typeName=0xb711c8e0 "QPoint")
at /home/devel/pyside/pyside_install/include/shiboken/typeresolver.h:84
#7 0xb70264b7 in init_QPoint (module=0xb6954914) at
/home/devel/pyside/pyside-shiboken/PySide/QtCore/PySide/QtCore/qpoint_wrapper.cpp:714
#8 0xb70b032f in initQtCore () at
/home/devel/pyside/pyside-shiboken/PySide/QtCore/PySide/QtCore/qtcore_module_wrapper.cpp:881
#9 0x080f3504 in _PyImport_LoadDynamicModule ()
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
