Can anyone tell me why I can't get Apache::DB to work with the
following config?
In the PERLDB block, if I change the Location to '/perl-status', the
debugger activates fine. However, when its set to '/pa/session', I
never see the debugger. I just see the output from the response
handler in the
Hi Steve,
>>
>>PerlInitHandler Apache::DB
>>
Just being curious:
I've seen PerlInitHandler Apache::DB a couple of times now, while the POD
recommends PerlFixupHandler +Apache::DB
Any specific reason for that?
-Thomas
Yeah, it turns out it works using the fixup handler. Odd thing is, it
works in the Init handler if I am debugging perl-status--just not
anything else.
On Mon, 2006-03-06 at 11:31 -0800, Gokul P. Nair wrote:
> In other words, is there any way to attach the perl debugger with a
> specific httpd pid, without having to restart Apache in a single
> worker thread mode to ensure that the perl debugger attaches to the
> right httpd pid?
No. You have no
Title: RE: Apache::DB - What am I doing wrong?
I don't think that is what he was asking... He asked if there was a way to attache the DEBUGGER to a specific pid; he did not address the issue of getting the correct input to that pid.
I do not use the debugger [but embed debugging code
On 6 Mar 2006, at 19:54, Chris Werner wrote:
I don't think that is what he was asking... He asked if there was a
way to attache the DEBUGGER to a specific pid; he did not address
the issue of getting the correct input to that pid.
The point is that you could not know which pid to attach to - y
On Mon, 2006-03-06 at 13:54 -0600, Chris Werner wrote:
> I don't think that is what he was asking... He asked if there was a
way to attache the
> DEBUGGER to a specific pid; he did not address the issue of getting
the correct input to
> that pid.
The one isn't much good without the other.
In theo
Since we are on this topic, is there any way to get Apache::DB to start the perl debugger without having to restart Apache with a single worker thread (i.e. httpd -X ... option)?In other words, is there any way to attach the perl debugger with a specific httpd pid, without having to restart Apache
i've never used the debugger, so this is a shot in the dark:
push the pid into a textfile / sql / sqlite
do a sql/sqlite lookup at the start of the request
attach the debugger if the current pid is in the result, detach/
notihing otherwise
On Mar 6, 2006, at 3:00 PM
Well, here's the deal. I would like to view a stack trace of everything that's being called in my web application, starting from when the web page is loaded to browsing through the different pages. Starting with the -X is certainly not an option in my case since the Apache server I'm using is maint
: Perrin Harkins; Chris Werner
Cc: Gokul P. Nair; modperl_users
Subject: RE: Apache::DB - What am
I doing wrong?
Well, here's the deal. I would like to view a stack trace of everything
that's being called in my web application, starting from when the web page is
loaded to browsing t
Also, when I said "use Carp in every module", I meant 'call Carp::Cluck'. Sorry for that confusion. Gokul"Gokul P. Nair" <[EMAIL PROTECTED]> wrote: Well, here's the deal. I would like to view a stack trace of everything that's being called in my web application, starting from when the web page is
On Mon, 2006-03-06 at 12:38 -0800, Gokul P. Nair wrote:
> Starting with the -X is certainly not an option in my case since the
> Apache server I'm using is maintained by another dept and all i have
> is access to start, stop or restart the server though a script.
Unless they've gone to a lot of t
13 matches
Mail list logo
