hi,
I'd like to set a breakpoint at the first line in the module's handler,
sub handler {
my $r = shift; <-- here
... ...
$r->set_handlers(PerlResponseHandler => \&contentHandler);
}
So, I tried PerFixupHandler, PerlHandler and PerlInitHander
respectively in below L
What sort of IDE, debugger, and platform are you using?
Personally for debugging handlers I find it easier to just stick a line
like: warn "got here, r=$r\n"
then just tail -f the error_log. Proper old school. Then again I
develop with vi on an 80x24 terminal, am I missing out on something?
No IDE for me too, I am using vi on a Debian terminal too.
warn is easy and good, I also want a more common and more powerful
interactive debugger tool, now I am trying Apache::DB and have this
trouble.
On 2/7/06, John ORourke <[EMAIL PROTECTED]> wrote:
> What sort of IDE, debugger, and platform a
Ken Perl wrote:
No IDE for me too, I am using vi on a Debian terminal too.
warn is easy and good, I also want a more common and more powerful
interactive debugger tool, now I am trying Apache::DB and have this
trouble.
My bad... I was completely unaware of Apache::DB!
John
On 2/7/06, Joh
On Tue, 7 Feb 2006 16:10:47 +0800
Ken Perl <[EMAIL PROTECTED]> wrote:
> hi,
> I'd like to set a breakpoint at the first line in the module's
> handler, sub handler {
> my $r = shift; <-- here
> ... ...
>$r->set_handlers(PerlResponseHandler => \&contentHandler);
> }
On Tue, 2006-02-07 at 16:10 +0800, Ken Perl wrote:
> hi,
> I'd like to set a breakpoint at the first line in the module's handler,
> sub handler {
> my $r = shift; <-- here
> ... ...
>$r->set_handlers(PerlResponseHandler => \&contentHandler);
> }
>
> So, I tried Per
You catched my problem, I didn't load debugger before this handler, thanks.
After I changed the order in the httpd config file, my problem is
solved, It stopped at the point I wanted,
my $r = shift;
Thanks again.
On 2/8/06, Perrin Harkins <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-02-07 at 16:1