On Mon, Jun 13, 2011 at 10:14 PM, Uri Moszkowicz wrote:
> Ah I see the note on the FAQ about the tty:
> "When using vim, the debuggee output is redirected to /dev/null. So in this
> case you must tell gdb to redirect the debuggee output to another terminal."
> From your response, it sounds like this restriction still exists even with
> the latest version of the software. Do you have plans to fix this?

You must get the last development version from the repository, see
http://pyclewn.sourceforge.net/mercurial.html
When you have another terminal available, run 'inferior_tty.py' in
this terminal. 'inferior_tty.py' is installed with pyclewn.
'inferior_tty.py' will create a pseudo tty that is fit to be used as
gdb inferior tty, and it will print the name of this terminal so that
you can run ':Cset inferior-tty /dev/xxx' BEFORE starting the inferior
from gdb.


> On Mon, Jun 13, 2011 at 4:09 PM, Uri Moszkowicz <[email protected]> wrote:
>>
>> My vim script is attached. I was using \032 to interrupt the process but
>> it seems that won't work anymore. Using mapkeys I can map C-Z at least
>> however S-X doesn't work for me. I get an error about an invalid line
>> number.

You should map your interrupt key to 'Csigint' instead.
What is the error message with 'S-X' ?


>> I run vim within a text terminal and starting an xterm is not an option.
>> Is there something that I can do so that it appears in the
>> "(clewn)_console"? I tried setting inferior-tty to /dev/tty and my pty but
>> no luck. The first causes program to exit with code 1. The second causes GDB
>> to return an error that it is unable to control the pty.

--
Xavier

Les Chemins de Lokoti: http://lokoti.alwaysdata.net

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general

Reply via email to