Re^3: LWP error 500 read timeout "internal response"

Blame/credit me for most of the Perl debugger in Komodo. The part that talks to Perl is based on the 5.8 perl5db.pl library, but it differs quite a bit, given that it's a graphical debugger. I've seen this bug come and go over the years. I can't repro this particular bug on Windows, but certainly can on Linux, but only with certain sites (perlmonks.org yes, wired.com no). The debugger doesn't override any core routines. Any insight as to what's going on would be a great help. The timeout occurs on the first attempt to read from the socket. Doing something like this doesn't make a difference: $ua->timeout(1_000_000) if $^P; # has no effect

Comment on Re^3: LWP error 500 read timeout "internal response"

Replies are listed 'Best First'.
Re^4: LWP error 500 read timeout "internal response" by ericp (Initiate) on May 31, 2007 at 23:41 UTC
The fix, for people running version Komodo 4.0 or 4.1, is to tell the debugger not to use the alarm() function internally. Make sure the value of the `PERLDB_OPTS` environment variable includes `alarm=0`. You can set this either before Komodo is launched, or in `Preferences\|Environment`. If anyone's wondering why, it's because I use the alarm() function to poll for a `break` command from the debugger client (usually Komodo) to see if I should set `$DB::single` to 1.	[reply]

Replies are listed 'Best First'.

Re^4: LWP error 500 read timeout "internal response"
by ericp (Initiate) on May 31, 2007 at 23:41 UTC

PERLDB_OPTS

alarm=0

Preferences|Environment

If anyone's wondering why, it's because I use the alarm() function to poll for a break command from the debugger client (usually Komodo) to see if I should set $DB::single to 1.

[reply]