On Tue, Nov 2, 2010 at 3:49 PM, Rob wrote:
>
> Will do. I also get occasional "gdb ERROR all cmds have not been
> processed in results" mixed up with the source code in vim
> (sometimes after ctrl-z, setting breakpoints etc). Could that be
> related?
>
Yes indeed, it shows that the dialog between gdb and pyclewn is
broken.
To avoid the messages scrambling vim display, you may have them logged
in a 'logfile' file instead with:
pyclewn --level=error --file=logfile 2>/dev/null
If you don't mind, instead of using strace, could you please set the
maximum level of traces in pyclewn and send me the resulting
'logfile' when the problem occurs:
pyclewn --level=nbdebug --file=logfile 2>/dev/null
Alternatively it may be relevant to download and build gdb 7.2 (quite
simple, and you do not need to install it) and see if the problem
occurs there also. The gdb/mi interface (used for the dialog between
gdb and pyclewn) is still evolving, see the thread:
http://thread.gmane.org/gmane.comp.gdb.devel/28979
which is a bug report on gdb/mi that I sent to gdb-dev last august,
just as gdb 7.2 was on the point of being released.
--
Xavier
Les Chemins de Lokoti: http://lokoti.alwaysdata.net
------------------------------------------------------------------------------
Achieve Improved Network Security with IP and DNS Reputation.
Defend against bad network traffic, including botnets, malware,
phishing sites, and compromised hosts - saving your company time,
money, and embarrassment. Learn More!
http://p.sf.net/sfu/hpdev2dev-nov
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general
