Sometimes, errors in CodeRunner code are NOT raised / trapped

[GoogleCodeExporter]

I have seen this on three different occasions, but have not been able to
reproduce.  With the exact same network, everything works as it should
after a restart of DeVIDE.

Sometimes, code in the Excute tab of the CodeRunner will raise an exception
that is NOT trapped (or output anywhere!) during network execution.  What
should happen is that any errors should be trapped and shown to the user.

Original issue reported on code.google.com by cpbotha on 18 Sep 2008 at 12:12

[GoogleCodeExporter]

Possibly related: import pdb; pdb.set_trace() in the top-part of a CodeRunner, 
now
run the network.  Why does the pdb prompt appear in the bottom-half of the 
CodeRunner
and not in the main console window?

Original comment by cpbotha on 18 Sep 2008 at 5:03

[GoogleCodeExporter]

Hint: could it be that the saving / restoring of exception information in the 
VTK
observer event handler is screwing things over?

Original comment by cpbotha on 25 Sep 2008 at 8:32