On Thu, Aug 26, 2010 at 5:13 PM, Rob wrote: > I have been having a few issues with gdb 7.1, vim 7.3 and pyclewn 1.3: > > 1) "Program exited normally" but I can't regain control of gdb "gdb > busy: command discarded, please retry". Ctrl-Z in vim or :Csigint > results in "Quit" in the gdb window but has no other effect. > > 2) I sometimes see "gdb ERROR all cmds have not been processed in > results" in the source window, often next to a disabled breakpoint. > > 3) I can't easily close items in the watch window: only when I add, > delete or expand another variable is the first closed. On occasion > the contents of watch window don't change when the output from the > gdb 'print' command does show a change. > > Any ideas? >
Hi Rob, I cannot reproduce any of these issues on gdb 7.1, vim 7.3 and pyclewn 1.3 (linux debian). What operating system are you running ? Are these problems occasional or easy to reproduce with a test case. Is it possible to get the logs of these issues (pyclewn -l nbdebug -f logfile 2>/dev/null). Side note: from 2) I assume you are running vim, not gvim. In this case, error messages are printed on sys.stderr and that scrambles vim display. I will fix it. Xavier ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
