You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl-cvs@perl.apache.org by st...@apache.org on 2001/09/19 19:03:17 UTC
cvs commit: modperl SUPPORT
stas 01/09/19 10:03:17
Modified: . SUPPORT
Log:
setting env for getting the core file dumped note
Revision Changes Path
1.17 +13 -0 modperl/SUPPORT
Index: SUPPORT
===================================================================
RCS file: /home/cvs/modperl/SUPPORT,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- SUPPORT 2000/06/09 17:15:59 1.16
+++ SUPPORT 2001/09/19 17:03:17 1.17
@@ -143,6 +143,19 @@
Rebuild httpd/mod_perl with PERL_DEBUG=1, let's see a new backtrace.
+If you get a segfault but no core file gets dumped and you cannot
+reproduce the segfault on will, you have to make sure that your
+environment is set to allow a core file to be dumped. Change the
+script that starts the server to do (in bash):
+
+ ulimit -c unlimited
+
+before the code that starts the server. Alternatively you can execute
+this command from the shell and then start the server from the same
+shell. Now you should be able to get the core dumped.
+
+Of course the directory the server is running in (usually as defined
+by ServerRoot) should be writable as well.
=item SPINNING PROCESSES