🚀 go-pugleaf

I'm a real fan of gdb's tty option. Its great for debugging a "screen"
application in one window, with the debugger output in another.

The one thing I find awkward though is stopping the "inferior" with an
INTR signal from the keyboard.

My first expectation was that I could type something in the debugger
window to stop the inferior. That doesn't work. gdb is stuck on a wait
looking for an event in the inferior. It reads no input and has its own
INTR disabled.

In fact you can deliver the INTR directly to the inferior's tty and as
usual, the inferior stops and gdb comes back from the wait. The trouble
is that one important use of the tty option is debugging screen
oriented programs that may well be in raw mode, with no keyboard
generated INTR's.

You can deliver the signal by hand from a third window, by doing a ps
and using kill. It seems like a better idea would be to fix gdb, to
listen for its own INTR and have a handler that would forward the
signal to the inferior (maybe after a prompt "Signal Inferior?).

-- 
Ken Mandelberg      | km@mathcs.emory.edu          PREFERRED
Emory University    | {decvax,gatech}!emory!km     UUCP 
Dept of Math and CS | km@emory.bitnet              NON-DOMAIN BITNET  
Atlanta, GA 30322   | Phone: (404) 727-7963