cvs commit: modperl/src/modules/perl mod_perl.c

[cholet]

cholet  00/06/02 10:23:08

  Modified:src/modules/perl mod_perl.c
  Log:
  fix segfault
  
  Revision  ChangesPath
  1.122 +1 -1  modperl/src/modules/perl/mod_perl.c
  
  Index: mod_perl.c
  ===
  RCS file: /home/cvs/modperl/src/modules/perl/mod_perl.c,v
  retrieving revision 1.121
  retrieving revision 1.122
  diff -u -r1.121 -r1.122
  --- mod_perl.c2000/05/25 18:06:23 1.121
  +++ mod_perl.c2000/06/02 17:23:07 1.122
  @@ -1222,7 +1222,7 @@
   }
   
   #ifdef CVf_METHOD
  -if (CvFLAGS(cv) & CVf_METHOD) {
  +if (cv && (CvFLAGS(cv) & CVf_METHOD)) {
   is_method = 1;
   }
   #endif
  
  
  

cvs commit: modperl SUPPORT

[cholet]

cholet  00/06/02 10:06:39

  Modified:.SUPPORT
  Log:
  add Doug's snippet about spinning processes
  
  Revision  ChangesPath
  1.15  +11 -0 modperl/SUPPORT
  
  Index: SUPPORT
  ===
  RCS file: /home/cvs/modperl/SUPPORT,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- SUPPORT   2000/03/03 00:30:52 1.14
  +++ SUPPORT   2000/06/02 17:06:38 1.15
  @@ -157,5 +157,16 @@
   
   Rebuild httpd/mod_perl with PERL_DEBUG=1, let's see a new backtrace.
   
  +
  +=item SPINNING PROCESSES
  +
  +If a process is spinning (seemingly stuck in an endless loop, eating
  +up all cpu), you can use gdb to find which Perl code is causing the
  +spin:
  +
  +% gdb httpd 
  +(gdb) source modperl_x.xx/.gdbinit
  +(gdb) curinfo
  +
   =back