| Subject: | Devel::ebug::Console: Possible typo that prevents codelines from getting cached (and slows down show_codelines) |
| Date: | Fri, 6 Jul 2007 16:16:22 +0900 |
| To: | bug-Devel-ebug [...] rt.cpan.org |
| From: | "Faiz Kazi" <faiz.kazi [...] gmail.com> |
Hullo,
Thanks so much for having written ebug; it's been extremely useful to
me already, though I just starting using it last week.
I was trying out ebug over a slow network (a process running with
-d:ebug::Backend on a server, and a remote client (see below for the
client script)).
When using the "l" command in the client debugger console, it seems
that all lines of the current source file are being pulled across the
network, though show_codelines (Console.pm, line 157 in the latest
release) is making efforts to cache the source for each file. This
means that when I step into a subroutine defined in a file that has a
large number of lines, showing the code-lines is very slow (especially
if "L" is toggled)
I think that a possible typo (see attached diff) may be the cause for this.
Distribution: Devel-ebug-0.48
Module: Devel::ebug::Console;
Perl Version: 5.6, 5.8.8 (any version actually)
OS: Linux 2.6.20 (Debian unstable) and Linux 2.4.x RHEL3
For the client script I basically used ebug-client, except that:
foreach ( 1 .. 10 ) {
$socket = IO::Socket::INET->new(
# Connect to a debugee far, far away
PeerAddr => $ARG->{host} || 'localhost',
PeerPort => $ARG->{port},
Proto => 'tcp',
Reuse => 1,
ReuserAddr => 1,
);
last if $socket;
sleep 1;
}
Thanks,
Fuzz
Message body is not shown because sender requested not to inline it.