Hi,
I have the latest mercurial version installed but this does not seem to work
correctly:
gdb process terminated after receiving signal 11.
Closing this gdb session.
===========
Pyclewn version 1.5 starting a new instance of gdb.
Quit
gdb busy: command discarded, please retry
gdb busy: command discarded, please retry
gdb busy: command discarded, please retry
Despite what the (clewn)_console says there is no gdb process running, and any
command such as Crun results in the above busy message.
The log file only contained "gdb ERROR all cmds have not been processed in
results" but I wasn't running with nbdebug.
Unfortunately (or fortunately) gdb problems aren't common enough to reproduce
this. If I kill gdb with 'kill -11', pyclewn does restart it correctly. Could
pyclewn or the netbeans interface be in the wrong state in the above case?
thanks,
Rob
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general
