Thanks, toma, for trying this out. You are doing great.
Sorry that I forgot about this snag. With both your
interactive shell and the Perl debugger trying to read from
your tty, the reads will interleave and not match up well
with the prompts.
So your shell wrote out a prompt and then requested a read.
Next, the debugger wrote out a prompt and then requested
a read. The shell's request for a read was still active
and so the next line you type goes to the shell even though
what you see is a debugger prompt. The debugger is still
waiting for its read to complete so the CGI goes nowhere.
The simplest solution is to just tell your interactive shell
to stop reading from your tty for a while. I'd usually do
something like "sleep 6000". Then I could interact with
the debugger fine. When done debugging that session, an
interupt (usually CTRL-C) would give me back my interactive
shell prompt.
A second telnet session can also be useful so you aren't
tempted to try to get your interactive shell prompt back
while still debugging. (:
-
tye
(but my friends call me "Tye")