[PyQt] Re: [Pyqwt-users] segfaults on linux and mac with sip 4.7.6

Erick Tryzelaar idadesub at users.sourceforge.net
Sat May 31 02:42:38 BST 2008


Actually, this is happening because the pyqwt is doing an "import
PyQt4.Qt", which is the thing that's actually segfaulting.

On Fri, May 30, 2008 at 6:29 PM, Discussion and help list for PyQwt
users <pyqwt-users at lists.sourceforge.net> wrote:
> I've had a couple different module segfault with a stack trace similar to this:
>
> 0   sip.so                              0x04434fd8 createType + 249
> 1   sip.so                              0x04430973 sip_api_export_module + 865
> 2   _qt.so                              0x01704f0e sip_init_QtWebKit() + 190
> 3   _qt.so                              0x017b3dab sip_init + 39
> 4   org.python.python                   0x00174dd6 PyObject_CallMethod + 182
> 5   QtWebKit.so                         0x0446cfae initQtWebKit + 72
> 6   org.python.python                   0x0020bc97 _PyImport_LoadDynamicModule + 167
> 7   org.python.python                   0x00209b03 load_module + 227
> 8   org.python.python                   0x0020a35d import_submodule + 301
> 9   org.python.python                   0x0020a59a load_next + 170
> 10  org.python.python                   0x0020aad3 PyImport_ImportModuleEx + 227
> 11  org.python.python                   0x001dbf49 builtin___import__ + 121
> 12  org.python.python                   0x00174bd6 PyObject_CallFunction + 134
> 13  org.python.python                   0x0020af3f PyImport_Import + 191
> 14  org.python.python                   0x0020b117 PyImport_ImportModule + 39
> 15  Qt.so                               0x010e6dd0 sip_import_component_module + 22
> 16  Qt.so                               0x010e6ed2 initQt + 198
> 17  org.python.python                   0x0020bc97 _PyImport_LoadDynamicModule + 167
> 18  org.python.python                   0x00209b03 load_module + 227
> 19  org.python.python                   0x0020a35d import_submodule + 301
> 20  org.python.python                   0x0020a59a load_next + 170
> 21  org.python.python                   0x0020aad3 PyImport_ImportModuleEx + 227
> 22  org.python.python                   0x001dbf49 builtin___import__ + 121
> 23  org.python.python                   0x001706a2 PyObject_Call + 50
> 24  org.python.python                   0x001e4806
> PyEval_CallObjectWithKeywords + 118
> 25  org.python.python                   0x001e6d91 PyEval_EvalFrame + 5809
> 26  org.python.python                   0x001ea4dd PyEval_EvalFrame + 19965
> 27  org.python.python                   0x001ea4dd PyEval_EvalFrame + 19965
> 28  org.python.python                   0x001ea4dd PyEval_EvalFrame + 19965
> 29  org.python.python                   0x001ebc5f PyEval_EvalCodeEx + 1631
> 30  org.python.python                   0x001ebf27 PyEval_EvalCode + 87
> 31  org.python.python                   0x00213e47 PyRun_FileExFlags + 231
> 32  org.python.python                   0x00214143 PyRun_SimpleFileExFlags + 659
> 33  org.python.python                   0x0021ea7a Py_Main + 3130
> 34  org.python.python                   0x000018db 0x1000 + 2267
> 35  org.python.python                   0x00001809 0x1000 + 2057
>
>
> This particular trace is coming from compiling pyqwt, but we also get
> the same error trying to import PyQt4.QtHelp and some other modules.
> Has anyone else run into this?
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Pyqwt-users mailing list
> Pyqwt-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pyqwt-users
>


More information about the PyQt mailing list