On Mon, Feb 18, 2013 at 2:50 PM, Rob wrote: > I have started seeing this message written to (clewn)_console after setting > a breakpoint and stopping at it. The message is also printed after each of > the first 9 frames of a back trace. It is the same in pyclewn 1.10.py2 & > pyclewn 1.8.py2. See also the attached log output.
Hi Rob, Thanks for the report. It seems that the python exception IndexError is raised by gdb. The line: gdb DEBUG &"Python Exception <type 'exceptions.IndexError'> list index out of range: \n" in your log is a gdb/mi stream record that "contains debugging messages being produced by gdb's internals" (quote from gdb doc). What version of gdb are you using and do you extend gdb with python ? Is it easy to reproduce and can you reproduce it with the gdb command line interface ? -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
