On Thursday 23 June 2011, 08:28:06 David Townshend wrote: > If it vanishes, it implies a segfault which you will probably see if > you run idle form the command line. You should be able to get a > backtrace by running idle through gdb, i.e, from the command line, > run "gdb idle". Then in gdb type "run". Idle should start as usual, > so get it to crash. Then within gdb type "bt". This will give a > backtrace which will hopefully at least point to whether its python, > pyqt or qt.
Close, but no cigar. after installing assorted .debug packages of python(3), sip, qt, PyQt, and probably glibc, glib, libstdc++, you usually invoke a python script with gdb similar to: gdb python3 -ex "set args /usr/bin/idle" -ex run Hth, Pete _______________________________________________ PyQt mailing list PyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt