[PyKDE] eric3 possible annomoly ?
Im using eric3.4.2 quite heavily have found an annomoly. I write a simple test script, right click showprofile data, it is greyed out as expected ... :-) I 'Ps' run the script within eric3 I now right click showprofile data, it is still greyed out - not as expected :-( If I shut down eric3 re-boot it, right click showprofile data and it is there, click it and the profile data is there. If I then right click erase all info the info stays on the display. Click OK, right click showprofile data, it is again greyed out as expected ... This is not a serious problem .. In fact with my steep learning curve it could be me not operating eric3 properly. Can anyone shed any light ? Dave ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] eric3 possible annomoly ?
Hi, Am Sonntag, 20. Juni 2004 13:13 schrieb Dave S: Im using eric3.4.2 quite heavily have found an annomoly. I write a simple test script, right click showprofile data, it is greyed out as expected ... :-) I 'Ps' run the script within eric3 I now right click showprofile data, it is still greyed out - not as expected :-( I just tried to reproduce your problem with my testscripts and everything was working ok. Please mail your script, which is showing the described behavior. If I shut down eric3 re-boot it, right click showprofile data and it is there, click it and the profile data is there. If I then right click erase all info the info stays on the display. Click OK, right click showprofile data, it is again greyed out as expected ... The Erase ... entries erase the profile and/or timing data on disk, not the display. That's why the menu entry is grayed out. This is not a serious problem .. In fact with my steep learning curve it could be me not operating eric3 properly. Can anyone shed any light ? Dave Detlev -- Detlev Offenbach [EMAIL PROTECTED] ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Segmentation faults in pyqt
Hi, This smells fishy. I would start checking your system for old versions of sip/PyQt, especially in /usr/lib/python. If this guess doesn't match, send us the output of: I did that - I removed all things that appeared to be part of sip and pyqt, and reinstalled the packages. Now all in /usr/lib/python2.3/site-packages is from the same date (2004-05-21) and the libsip is from 2004-04-24. Still the same behaviour :( python -vc import qt I attached the output - from what I understand, it looks ok. These are the various versions of sip/pyqt I tried: sip-4.0rc3 sip-snapshot-20040329 sip-4.0rc4 sip-snapshot-20040501 Note that changing sip always implies a PyQt (and dependants) recompile. Sure - I of course did that. Good luck, Thanks, but none so far :( Regards, Diez # installing zipimport hook import zipimport # builtin # installed zipimport hook # /usr/lib/python2.3/site.pyc matches /usr/lib/python2.3/site.py import site # precompiled from /usr/lib/python2.3/site.pyc # /usr/lib/python2.3/os.pyc matches /usr/lib/python2.3/os.py import os # precompiled from /usr/lib/python2.3/os.pyc import posix # builtin # /usr/lib/python2.3/posixpath.pyc matches /usr/lib/python2.3/posixpath.py import posixpath # precompiled from /usr/lib/python2.3/posixpath.pyc # /usr/lib/python2.3/stat.pyc matches /usr/lib/python2.3/stat.py import stat # precompiled from /usr/lib/python2.3/stat.pyc # /usr/lib/python2.3/UserDict.pyc matches /usr/lib/python2.3/UserDict.py import UserDict # precompiled from /usr/lib/python2.3/UserDict.pyc # /usr/lib/python2.3/copy_reg.pyc matches /usr/lib/python2.3/copy_reg.py import copy_reg # precompiled from /usr/lib/python2.3/copy_reg.pyc # /usr/lib/python2.3/types.pyc matches /usr/lib/python2.3/types.py import types # precompiled from /usr/lib/python2.3/types.pyc # /usr/lib/python2.3/warnings.pyc matches /usr/lib/python2.3/warnings.py import warnings # precompiled from /usr/lib/python2.3/warnings.pyc # /usr/lib/python2.3/linecache.pyc matches /usr/lib/python2.3/linecache.py import linecache # precompiled from /usr/lib/python2.3/linecache.pyc import encodings # directory /usr/lib/python2.3/encodings # /usr/lib/python2.3/encodings/__init__.pyc matches /usr/lib/python2.3/encodings/__init__.py import encodings # precompiled from /usr/lib/python2.3/encodings/__init__.pyc # /usr/lib/python2.3/codecs.pyc matches /usr/lib/python2.3/codecs.py import codecs # precompiled from /usr/lib/python2.3/codecs.pyc import _codecs # builtin # /usr/lib/python2.3/encodings/aliases.pyc matches /usr/lib/python2.3/encodings/aliases.py import encodings.aliases # precompiled from /usr/lib/python2.3/encodings/aliases.pyc # /usr/lib/python2.3/encodings/iso8859_15.pyc matches /usr/lib/python2.3/encodings/iso8859_15.py import encodings.iso8859_15 # precompiled from /usr/lib/python2.3/encodings/iso8859_15.pyc Python 2.3.4 (#2, May 29 2004, 03:31:27) [GCC 3.3.3 (Debian 20040417)] on linux2 Type help, copyright, credits or license for more information. # /usr/lib/python2.3/site-packages/qt.pyc matches /usr/lib/python2.3/site-packages/qt.py import qt # precompiled from /usr/lib/python2.3/site-packages/qt.pyc import libsip # dynamically loaded from /usr/lib/python2.3/site-packages/libsip.so import libqtc # dynamically loaded from /usr/lib/python2.3/site-packages/libqtcmodule.so # clear __builtin__._ # clear sys.path # clear sys.argv # clear sys.ps1 # clear sys.ps2 # clear sys.exitfunc # clear sys.exc_type # clear sys.exc_value # clear sys.exc_traceback # clear sys.last_type # clear sys.last_value # clear sys.last_traceback # clear sys.path_hooks # clear sys.path_importer_cache # clear sys.meta_path # restore sys.stdin # restore sys.stdout # restore sys.stderr # cleanup __main__ # cleanup[1] site # cleanup[1] encodings # cleanup[1] _codecs # cleanup[1] zipimport # cleanup[1] warnings # cleanup[1] encodings.iso8859_15 # cleanup[1] types # cleanup[1] qt # cleanup[1] signal # cleanup[1] linecache # cleanup[1] posix # cleanup[1] encodings.aliases # cleanup[1] exceptions # cleanup[1] libqtc # cleanup[1] libsip # cleanup[1] codecs # cleanup[2] copy_reg # cleanup[2] posixpath # cleanup[2] os.path # cleanup[2] stat # cleanup[2] UserDict # cleanup[2] os # cleanup sys # cleanup __builtin__ # cleanup ints: 83 unfreed ints in 6 out of 7 blocks # cleanup floats dlopen(/usr/lib/python2.3/site-packages/libsip.so, 2); dlopen(/usr/lib/python2.3/site-packages/libqtcmodule.so, 2);
Re: [PyKDE] Segmentation faults in pyqt
libsip is SIP v3, not v4. Yes, I currently used the debian packages, which are sip 3.10.1 and pyqt 3.11 In the meantime, I created a debug-builds of python 2.3.4, sip 4 rc4 and pyqt 3.12 Still the same problem - so it appears to me that the problem is not something stale lying around. When I gdb tut3.py (Unfortunately I'm no gdb expert - not anymore, at least...) I get a segfault with this stack: #0 0x41c84829 in _Xutf8DefaultDrawImageString () from /usr/X11R6/lib/X11/locale/lib/common/xomGeneric.so.2 #1 0x41c84f73 in _Xutf8DefaultDrawImageString () from /usr/X11R6/lib/X11/locale/lib/common/xomGeneric.so.2 #2 0x41c851ea in _Xutf8DefaultDrawImageString () from /usr/X11R6/lib/X11/locale/lib/common/xomGeneric.so.2 #3 0x41c8552f in _Xutf8DefaultDrawImageString () from /usr/X11R6/lib/X11/locale/lib/common/xomGeneric.so.2 #4 0x41c85868 in _Xutf8DefaultDrawImageString () from /usr/X11R6/lib/X11/locale/lib/common/xomGeneric.so.2 #5 0x41c85e09 in destroy_fontdata () from /usr/X11R6/lib/X11/locale/lib/common/xomGeneric.so.2 #6 0x4142f461 in XCreateOC () from /usr/X11R6/lib/libX11.so.6 #7 0x4142e7f5 in XCreateFontSet () from /usr/X11R6/lib/libX11.so.6 #8 0x40d71345 in QMapPrivateQFont::Script, QString::clear () from /usr/lib/libqt-mt.so.3 #9 0x40d71fe1 in QInputContext::QInputContext () from /usr/lib/libqt-mt.so.3 #10 0x40d9122c in QWidget::createInputContext () from /usr/lib/libqt-mt.so.3 #11 0x40d58798 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #12 0x40d6e7d4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #13 0x40dd7498 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #14 0x40dd7348 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #15 0x40dc3d51 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #16 0x40a04027 in meth_QApplication_exec_loop (sipSelf=0x41beed6c, sipArgs=0x401a5034) at sipqtpart0.cpp:426590 #17 0x0810ea96 in PyCFunction_Call (func=0x4021137c, arg=0x401a5034, kw=0x0) at Objects/methodobject.c:73 #18 0x080c38d0 in call_function (pp_stack=0xb784, oparg=0) at Python/ceval.c:3439 #19 0x080bffe6 in eval_frame (f=0x8166d1c) at Python/ceval.c:2116 #20 0x080c1de6 in PyEval_EvalCodeEx (co=0x401fd658, globals=0x401c1df4, locals=0x401c1df4, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:2663 #21 0x080ba6ac in PyEval_EvalCode (co=0x401fd658, globals=0x401c1df4, locals=0x401c1df4) at Python/ceval.c:537 #22 0x080e87a2 in run_node (n=0x401b9348, filename=0xbb84 examples3/tut3.py, globals=0x401c1df4, locals=0x401c1df4, flags=0xb958) at Python/pythonrun.c:1267 #23 0x080e8745 in run_err_node (n=0x401b9348, filename=0xbb84 examples3/tut3.py, globals=0x401c1df4, locals=0x401c1df4, flags=0xb958) at Python/pythonrun.c:1254 #24 0x080e8707 in PyRun_FileExFlags (fp=0x8155008, filename=0xbb84 examples3/tut3.py, start=257, globals=0x401c1df4, locals=0x401c1df4, closeit=1, flags=0xb958) at Python/pythonrun.c:1245 #25 0x080e7493 in PyRun_SimpleFileExFlags (fp=0x8155008, filename=0xbb84 examples3/tut3.py, closeit=1, flags=0xb958) at Python/pythonrun.c:862 #26 0x080e6cb7 in PyRun_AnyFileExFlags (fp=0x8155008, filename=0xbb84 examples3/tut3.py, closeit=1, flags=0xb958) at Python/pythonrun.c:659 #27 0x08055683 in Py_Main (argc=2, argv=0xba34) at Modules/main.c:415 #28 0x08054e36 in main (argc=2, argv=0xba34) at Modules/python.c:23 Googling gave me only one message from nov 2003 that stated a problem with ui-designer - nothing more so far. Does this give you an idea? I also get a segfault when starting qt designer: [EMAIL PROTECTED]:~/software/archives/PyQt-x11-gpl-3.12$ designer-qt3 KThemeStyle cache seems corrupt! Segmentation fault I wanted to chekt that to verify the message mentioned above - but this seems to be a different problem. I'll try to fix that one, too. Regards, Diez ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
