Thanks for the quick response Xavier! The issue seems to be that my process is hanging trying to do output. When I interrupt, it is stuck in some cout routines. When I increase the size of the output from the small script, I see the same issue. I also notice that no output comes out of the terminal that I started pyclewn from.
If I alter the output terminal as you suggest, everything is fine - but this seems sort of cumbersome?? What could be causing the output terminal to block output? I tried both xterm and the Regarding my installation - I had tried to reinstall, but the root path didn't include /usr/local/bin, so it just kept re-installing the 7.2 stuff - once I set up the path correctly, it was all fine. Phil -----Original Message----- From: Xavier de Gaye [mailto:[email protected]] Sent: Monday, June 04, 2012 12:00 PM To: Brooks, Phil Cc: [email protected] Subject: Re: [pyclewn] starting up pyclewn On Mon, Jun 4, 2012 at 7:47 PM, Brooks, Phil wrote: > > then I type: > > :Crun > > and it hangs indefinitely. I can't see that anything is happening > anywhere - no output from the terminal that I started pyclewn from - > the command shows up in the console window as (gdb) run - and the > :Crun text remains in the gvim command window and nothing else > happens. If I try any more Pyclewn commands that interact with gdb, > it complains about the debugger being busy. > Hi Phil, Can you interrupt the debuggee with ':Csigint' or <C-Z> ? You may also try to redirect the debuggee output to another terminal using the method described in the documentation: Use the "inferior_tty.py" script installed with pyclewn. This script creates a pseudo terminal to be used as the controlling terminal of the debuggee. From pyclewn, spawn an xterm terminal and launch "inferior_tty.py" in this terminal with this command run from Vim: :Cshell setsid xterm -e inferior_tty.py & "inferior_tty.py" prints the name of the pseudo terminal to be used by gdb. Copy and paste the command in Vim: :Cset inferior-tty /dev/pts/nn Then start the debuggee with ':Crun'. > I decided to upgrade to gvim 7.3 and then ran into a new problem > when I installed gvim 7.3 to /usr/local/bin - now I get the > following error message if /usr/local/bin is in my path: > > vim CRITICAL > Exception in pyclewn: > > <class 'clewn.ClewnError'> > "pyclewn.vim version does not match pyclewn's: > pyclewn version: "pyclewn-1.8.py2" > pyclewn.vim version: """ > source line: "% (pyclewn_version, version))" > at /usr/lib/python2.6/site-packages/clewn/vim.py:381 > > pyclewn aborting... To fix the problem reinstall pyclewn after the gvim 7.3 install. This is because pyclewn installs some files in Vim runtime environment and it is not the same environment in Vim 7.2 and Vim 7.3. See also INSTALL to install those Vim runtime files in your personal vim runtime directory instead so that you don't need to reinstall them after each new Vim release. Xavier ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
