1. compile with debug flag First make sure u install gdb, then compile httpd and modperl in debug mod, configure apache2 as: ./configure --enable-maintainer-mode and ur custom flages configure mod_perl ad: perl "Makefile.PL MP_DEBUG=1 and ur custom flages" compile and install them to the right place.
2. run apache2 in gdb $APACHE2_HOME is ur apache installed directory such as /usr/local/apache2 then run gdb as: gdb $APACHE2_HOME/bin/httpd (gdb) run -X -d $APACHE2_HOME
apache2 should run.
3. report the backtrace
visit ur page us usally, when server segfaults, gdb will tell ur where. u just type
(gdb) backtrace
and report the result.
hope it could help u.
[EMAIL PROTECTED] wrote:
I'm using apache v2.0.48 and have confirmed that the problem exists with both mod_perl v1.99_11 and v1.99_12-dev in CVS. If I simply use "RewriteEngine On", mod_perl works fine. If I use "RewriteEngine On<CR>RewriteRule ^/(.*) /index.pl/$1 [PT]" (or anything similar), the apache server immediately segfaults, displays nothing, and logs nothing useful (even in debug). This does not happen with mod_perl v1.99_10, although for reasons unrelated to mod_perl I'm actually stuck using v1.99_09 right now, which works more or less fine with this configuration. I'm using apache compiled from source on RedHat 8.0, with perl-5.8.0-88.3 and GCC v3.3.2.
Unfortunately I'm not a C programmer, or I probably would have been able to send more useful information. I tried to follow the instructions on debugging mod_perl C internals and get a core file, but I couldn't get that to work either. Any ideas? Thanks.
--Aaron
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
