segfault in qtconsole when kernel quits

[eteq]

This is reproducible in Ubuntu 10.10 - if I start a kernel with ipython-qtconsole, and then use the -e option to connect to it with another qtconsole, and close the kernel by exiting from the second qtconsole, the first one segfaults. The same seems to happen to the second qtconsole if I exit from the first. In either case, the one that the exit command was issued at seems to close correctly with no errors.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe80e3700 (LWP 17503)]
0x00000000004a0695 in PyEval_EvalFrameEx (f=
    Frame 0x2471190, for file /usr/local/lib/python2.6/dist-packages/zmq/eventloop/ioloop.py, line 270, in start (event_pairs=[]), 
    throwflag=) at ../Python/ceval.c:2740
2740    ../Python/ceval.c: No such file or directory.
    in ../Python/ceval.c

Occasionally instead of a segfault, I see the following at the terminal:

Error in sys.excepthook:

Original exception was:
Error in sys.excepthook:

Original exception was:

[epatters]

@ellisonbg
I'm re-assigning this to you, Brian, since it looks like the problem is with the ZMQ event loop.

If it turns out the problem is on the frontend side, feel free to give the ticket back to me.

[takluyver]

I got another different error message:

sys.excepthook is missing
lost sys.stderr
sys.excepthook is missing
lost sys.stderr

[minrk]

I can't reproduce this with current IPython master and pyzmq+zeromq 2.1.7. Is this still an issue?

I get clean exits with every combination I have tried.

[eteq]

Yes, I can no longer reproduce this in master w/ 2.1.7, so I'm closing the issue. Thanks!