client for the built-in debugger, test FAILs, name of the module?

["Gabor Szabo" <szabgab@gmail.com>]

Hi,

in preparation to add a debugger to Padre, the IDE I have started to write
a stand-alone module that will be a client for the built-in debugger.
That is it will hide all the networking between itself and the
debugger. Currently
In order to get quick feedback from the CPAN testers I have uploaded
it using the
name Padre::Debugger thought it will need another name to disassociate it
from Padre.  I'd be glad to hear your suggestions.
Here is the current version of the synopsis:


  use Padre::Debugger;
  my $debugger = Padre::Debugger->new(host => $host, port => $port);
  $debugger->listen;

  # this is the point where the external script need to be launched
  # in a forked code first setting
      # $ENV{PERLDB_OPTS} = "RemotePort=$host:$port"
  # then running
      # perl -d script

  my $out = $debugger->step_in;

  $out = $debugger->step_over;

  my ($module, $file, $row, $content, $prompt) = $debugger->step_in;
  my ($module, $file, $row, $content, $prompt, $return_value) =
$debugger->step_out;
  my ($value, $prompt) = $debugger->get_value('$x');

There are some failing test reports:
http://www.nntp.perl.org/group/perl.cpan.testers/2008/09/msg2211674.html
http://www.nntp.perl.org/group/perl.cpan.testers/2008/09/msg2211678.html
http://www.nntp.perl.org/group/perl.cpan.testers/2008/09/msg2211672.html

They all fail as the prompt given by the debugger is
  DB<77>
instead of
  DB<1>

This does not happen on my 5.10. Any idea why does it happen on that
smoke machine?


As said above I'd be glad for any help in naming the module.


Gabor

---

Follow-Ups from:

Andy Armstrong <andy@hexten.net>
Matt S Trout <matt-p5p@trout.me.uk>

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---