Re: Fwd: mod_perl interactive debugging

2008-06-03 Thread Frank Wiles
On Mon, 2 Jun 2008 01:30:33 +0800
william [EMAIL PROTECTED] wrote:

 Hello, my debugger is working fine now under mod_perl, I can exit from
 debugger just
  like normal 'q' command. But then the apache is still in debugging
  mode and single process. So I have to press CTRL+Z to get out to the
  normal shell prompt. But whenever I do that my apache would longer to
  start again. I didn't see any text being logged in the log file.
 
  How can I have a proper exit from the debugger as well as the apache
  to start a normal server ? Thanks

  Hi William, 

  You should be able to hit Ctrl+C which will cause the Apache child
  to exit and then you can restart it without debugging and not in
  single process mode. 

  Hope that helps. 

 ---
   Frank Wiles, Revolution Systems, LLC. 
 Personal : [EMAIL PROTECTED]  http://www.wiles.org
 Work : [EMAIL PROTECTED] http://www.revsys.com 



Fwd: mod_perl interactive debugging

2008-06-01 Thread william
-- Forwarded message --
From: william [EMAIL PROTECTED]
Date: Jun 1, 2008 6:11 PM
Subject: Re: mod_perl interactive debugging
To: Fred Moyer [EMAIL PROTECTED]


On 6/1/08, william [EMAIL PROTECTED] wrote:
  On 6/1/08, william [EMAIL PROTECTED] wrote:
On 6/1/08, Fred Moyer [EMAIL PROTECTED] wrote:
  william wrote:
 
   On 5/29/08, william [EMAIL PROTECTED] wrote:
  
On 5/29/08, Fred Moyer [EMAIL PROTECTED] wrote:
  william wrote:
 
   On 5/29/08, Perrin Harkins [EMAIL PROTECTED] wrote:
  
On Wed, May 28, 2008 at 3:33 AM, william [EMAIL PROTECTED]
  wrote:
   
   I put the following lines at the top of my startup.pl script
   use APR::Pool (); #specific for mod_perl 2
   use Apache::DB ();
   Apache::DB-init();
  
 
   Can you show us the part of httpd.conf where you call
startup.pl?
 
   I always place my debugger calls before any other modules load,
  usually
  right after mod_perl.so is loaded.
   
   
Thanks for the prompt reply, here it is.
   
 /etc/apache2/httpd.conf
   
 Directory /var/www/cgi-bin
  Options +ExecCGI
  AddHandler cgi-script cgi pl
 /Directory
   
 ServerName localhost
   
   
 # Alias /modperl/ /var/www/modperl/
   
 # IfDefine PERLDB
 # Perl
 #  use APR::Pool ();
 #   use Apache::DB ();
 #   Apache::DB-init;
   
 #   warn PERLDB executed;
 # /Perl
 # Location /modperl/
 #   PerlFixupHandler Apache::DB
 # /Location
 # /IfDefine
   
   
 #The startup script
 PerlRequire '/var/www/modperl/Apache2/startup.pl'
   
   
  
 
   I didn't see a LodModule directive in there anywhere - do
you have a line
  like 'LoadModule perl_module modules/mod_perl.so'?
 
   It looked like you were using mod_perl2, so it is very
likely that you have
  that line in there somewhere (I don't know of anyone who has
done a static
  build with mp2.
 
 
   hello, I am still looking for solution. When command
   sudo apache2 -X  -k restart
   The debugger would immediately startup at this shell ?
  
 
   The debugger will start once the first request to the server is made.
 
 
   
   
My apache configuration file is not just at the httpd.conf , I also
 have the apache2.conf
   
 I have this line in /etc/apache2/mods-enabled/perl.load
 LoadModule perl_module /usr/lib/apache2/modules/mod_perl.so
   
 Yes, I am using
 mod_perl/2.0.4
 Perl/v5.10.0
   
 I am able to run my perl script under mod_perl, without any problem.
   
   
  The debugger will start once the first request to the server is made.
   
   
So the debugger would appear in which shell ?
   
 I only get to see the debugging process in /var/log/apache2/error.log
 , but not able to have interactive debugging feature.
   
 Thanks.
   
   
 apache2.conf
 #
 # Based upon the NCSA server configuration files originally by
Rob McCool.
 #
 # This is the main Apache server configuration file.  It contains the
 # configuration directives that give the server its instructions.
 # See http://httpd.apache.org/docs/2.2/ for detailed information about
 # the directives.
 #
 # Do NOT simply read the instructions in here without understanding
 # what they do.  They're here only as hints or reminders.  If
you are unsure
 # consult the online docs. You have been warned.
 #
 # The configuration directives are grouped into three basic sections:
 #  1. Directives that control the operation of the Apache
server process as a
 # whole (the 'global environment').
 #  2. Directives that define the parameters of the 'main' or
'default' server,
 # which responds to requests that aren't handled by a virtual host.
 # These directives also provide default values for the settings
 # of all virtual hosts.
 #  3. Settings for virtual hosts, which allow Web requests to be sent to
 # different IP addresses or hostnames and have them handled by the
 # same Apache server process.
 #
 # Configuration and logfile names: If the filenames you specify for many
 # of the server's control files begin with / (or drive:/
for Win32), the
 # server will use that explicit path.  If the filenames do *not* begin
 # with /, the value of ServerRoot is prepended -- so
 /var/log/apache2/foo.log
 # with ServerRoot set to  will be interpreted by the
 # server as //var/log/apache2/foo.log.
 #
   
 ### Section 1: Global Environment
 #
 # The directives in this section affect the overall