#14365 [Com]: require_once() causes segfault
ID: 14365 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: iPlanet related Operating System: RedHat Linux 7.3 PHP Version: 4.3.0-dev New Comment: Wow! I managed to create a page that creates a segfault every time... Before PHP only crashed once in a while (once in 40 requests?) but now I finally have something reproducable. The only thing I did was adding an extra INSERT query to the end of a search.php script. Haven't tried to create a minimal testcase yet, just to glad tat I can finally do some more testing. BTW IMO it's a good idea to change this bug. It's not about require_once() but about canonicalize() crashing PHP 4.3.0 (and something on 4.2.3 that I haven't been able to pinpoint yet). And it's not limited to iPlanet servers. Are there any more ways to get more information out of PHP? Memory usage? Most used functions? That kind of information? I'm going to play a bit with standalone httpd's so I don't have to attach to a running server. Oh and is it possible to subscribe to a bug at bugs.php.net? Previous Comments: [2003-01-06 06:17:35] [EMAIL PROTECTED] We are using evals but the worst I could find was 65 evals on one page (the template system uses evals for nested blocks). The index page has a complex template and needs 55 evals, normal pages only need 4 or 5 evals. [2003-01-06 01:58:31] [EMAIL PROTECTED] I've read the backtrace page but the bt there doesn't show php filenames and linenumber.. But Sean mailed me that I should try 'bt full', I'll try that the next time. Anyway, as I said I'm using Apache and not iPlanet... The canonicalize problem only seems to occur on 4.3.0, PHP 4.2.3 seems to segfault on memcopy() [2003-01-05 09:33:15] [EMAIL PROTECTED] See http://bugs.php.net/bugs-generating-backtrace.php for details on making backtraces. The stack size appears to be a setting in the iPlanet configuration:Try modifying your ns/threads section to include a larger stacksize...the default one is 128*1024I ran into a stacksize problem on the recent redhat update (related to glibc) that was segfaulting on a dns lookup. I didn't associate it with the segfault I was getting for PHP (Including squirrelmail), but the segfault for SM is gone now for me after this fix and SM works perfectly. Try this sample: ns_section "ns/threads" ns_param stacksize [expr 256*1024] " (quoted from this bug report). I don't have and have never used iPlanet, so it's up to you to find out how to configure it. " [2003-01-05 09:07:05] [EMAIL PROTECTED] I would love to but I don't have a clue how I should do that :D I'm using Apache 1.3.26 and PHP 4.3.0 (but that one segfaults too often) and PHP 4.2.3 (segfaults too but less often, especially when we use a debug build and limit the MaxRequestsPerChild to 10. Nested evals()? Hmm, we shouldn't, I'll go and see if that can be the case. BTW how did Sean create that backtrace? It even shows in what PHP file and on what line Apache/PHP went down... [2003-01-02 11:54:51] [EMAIL PROTECTED] Can you try increasing your stack size as was suggested in one of the earlier responses? The latest backtrace looks *very* deep - are you using a lot of nested eval() calls ? The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/14365 -- Edit this bug report at http://bugs.php.net/?id=14365&edit=1
#14365 [Com]: require_once() causes segfault
ID: 14365 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: No Feedback Bug Type: iPlanet related Operating System: RedHat Linux 7.3 PHP Version: 4.3.0-dev New Comment: Grr. These damn segfaults are really driving me nuts. I've been having segfaults with other versions of PHP (up to 4.2.3). I'm using PHP 4.3.0 at the moment and the number of segfaults has only increased. Sometimes there are almost no segfaults (one every 5 minutes?) but sometimes I get stuff like this in the errorlog: [Wed Jan 1 21:34:02 2003] [notice] child pid 13840 exit signal Segmentation fault (11) [Wed Jan 1 21:34:03 2003] [notice] child pid 13833 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13831 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13816 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13810 exit signal Segmentation fault (11) [Wed Jan 1 21:34:20 2003] [notice] child pid 13837 exit signal Segmentation fault (11) [Wed Jan 1 21:34:45 2003] [notice] child pid 13883 exit signal Segmentation fault (11) [Wed Jan 1 21:34:50 2003] [notice] child pid 13878 exit signal Segmentation fault (11) [Wed Jan 1 21:34:51 2003] [notice] child pid 13887 exit signal Segmentation fault (11) [Wed Jan 1 21:34:51 2003] [notice] child pid 13859 exit signal Segmentation fault (11) [Wed Jan 1 21:34:52 2003] [notice] child pid 13882 exit signal Segmentation fault (11) [Wed Jan 1 21:35:24 2003] [notice] child pid 13904 exit signal Segmentation fault (11) [Wed Jan 1 21:35:31 2003] [notice] child pid 13898 exit signal Segmentation fault (11) [Wed Jan 1 21:35:31 2003] [notice] child pid 13892 exit signal Segmentation fault (11) [Wed Jan 1 21:35:36 2003] [notice] child pid 13909 exit signal Segmentation fault (11) [Wed Jan 1 21:35:39 2003] [notice] child pid 14006 exit signal Segmentation fault (11) [Wed Jan 1 21:35:40 2003] [notice] child pid 13908 exit signal Segmentation fault (11) [Wed Jan 1 21:35:44 2003] [notice] child pid 14009 exit signal Segmentation fault (11) [Wed Jan 1 21:35:46 2003] [notice] child pid 13903 exit signal Segmentation fault (11) [Wed Jan 1 21:35:52 2003] [notice] child pid 14017 exit signal Segmentation fault (11) [Wed Jan 1 21:36:11 2003] [notice] child pid 14015 exit signal Segmentation fault (11) [Wed Jan 1 21:36:17 2003] [notice] child pid 14023 exit signal Segmentation fault (11) [Wed Jan 1 21:36:33 2003] [notice] child pid 14016 exit signal Segmentation fault (11) [Wed Jan 1 21:36:42 2003] [notice] child pid 14019 exit signal Segmentation fault (11) [Wed Jan 1 21:36:45 2003] [notice] child pid 14043 exit signal Segmentation fault (11) This is making me and my users _very_ unhappy :\ With 4.2.3 I got: (gdb) bt #0 0x42082a0c in memcpy () from /lib/i686/libc.so.6 #1 0x08134f7d in _estrndup () #2 0x0810deb0 in php_var_unserialize () #3 0x0810e796 in php_var_unserialize () #4 0x0810dd7a in php_var_unserialize () #5 0x08106dbc in zif_unserialize () #6 0x08169483 in execute () #7 0x08145b8e in zend_execute_scripts () #8 0x0808a06a in php_execute_script () #9 0x081511ca in apache_php_module_main () #10 0x0808638c in php_restore_umask () #11 0x080863e5 in php_restore_umask () #12 0x08173363 in ap_invoke_handler () #13 0x08187e9b in ap_some_auth_required () #14 0x08187efc in ap_process_request () #15 0x0817ef05 in ap_child_terminate () #16 0x0817f173 in ap_child_terminate () #17 0x0817f4f0 in ap_child_terminate () #18 0x0817fac5 in ap_child_terminate () #19 0x081800ff in main () #20 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 But with 4.3.0 I get: (gdb) bt #0 0x4204a646 in canonicalize () from /lib/i686/libc.so.6 #1 0x08182ced in virtual_file_ex () #2 0x08093ba0 in expand_filepath () #3 0x08092d30 in php_check_specific_open_basedir () #4 0x08092f12 in php_check_open_basedir () #5 0x0809c303 in _php_stream_fopen_with_path () #6 0x0809d243 in php_unregister_url_stream_wrapper () #7 0x0809d94d in _php_stream_open_wrapper_ex () #8 0x0809dc3b in _php_stream_open_wrapper_as_file () #9 0x0809010e in zif_set_time_limit () #10 0x080a2573 in open_file_for_scanning () #11 0x080a26f7 in compile_file () #12 0x080a2898 in compile_filename () #13 0x080cc601 in execute () #14 0x080ca99a in execute () #15 0x080cc76f in execute () #16 0x080ca99a in execute () #17 0x080cc76f in execute () #18 0x080ca99a in execute () (execute continues) #1319 0x080cc76f in execute () #1320 0x080ca99a in execute () #1321 0x080cc76f in execute () #1322 0x080bac4e in zend_execute_scripts () #1323 0x08091b71 in php_execute_script () #1324 0x080cf14a in apache_php_module_main () #1325 0x08088a44 in ap_get_server_built () #1326 0x08088a9d in ap_get_server_built () #1327 0x081a1453 in ap_invoke_handler () #1328 0x081b5f8b in ap_some_auth_required
#14365 [Com]: require_once() causes segfault
ID: 14365 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: No Feedback Bug Type: iPlanet related Operating System: RedHat Linux 7.3 PHP Version: 4.3.0-dev New Comment: Oh, sorry. Forgot to mention what the site is running on. We're using Apache 1.3.26 with PHP as a module. Info page is over here: http://www.bokt.nl/klad/info.php It's a Redhat 7.3 box with: gcc version 2.96 2731 (Red Hat Linux 7.3 2.96-112) It's an Athlon 1800 XP with 1GB ram and phpBB is using MySQL (MyISAM tables) extensively. Some stats can be seen on: http://www.bokt.nl/stats/ Previous Comments: [2003-01-01 14:51:48] [EMAIL PROTECTED] Grr. These damn segfaults are really driving me nuts. I've been having segfaults with other versions of PHP (up to 4.2.3). I'm using PHP 4.3.0 at the moment and the number of segfaults has only increased. Sometimes there are almost no segfaults (one every 5 minutes?) but sometimes I get stuff like this in the errorlog: [Wed Jan 1 21:34:02 2003] [notice] child pid 13840 exit signal Segmentation fault (11) [Wed Jan 1 21:34:03 2003] [notice] child pid 13833 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13831 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13816 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13810 exit signal Segmentation fault (11) [Wed Jan 1 21:34:20 2003] [notice] child pid 13837 exit signal Segmentation fault (11) [Wed Jan 1 21:34:45 2003] [notice] child pid 13883 exit signal Segmentation fault (11) [Wed Jan 1 21:34:50 2003] [notice] child pid 13878 exit signal Segmentation fault (11) [Wed Jan 1 21:34:51 2003] [notice] child pid 13887 exit signal Segmentation fault (11) [Wed Jan 1 21:34:51 2003] [notice] child pid 13859 exit signal Segmentation fault (11) [Wed Jan 1 21:34:52 2003] [notice] child pid 13882 exit signal Segmentation fault (11) [Wed Jan 1 21:35:24 2003] [notice] child pid 13904 exit signal Segmentation fault (11) [Wed Jan 1 21:35:31 2003] [notice] child pid 13898 exit signal Segmentation fault (11) [Wed Jan 1 21:35:31 2003] [notice] child pid 13892 exit signal Segmentation fault (11) [Wed Jan 1 21:35:36 2003] [notice] child pid 13909 exit signal Segmentation fault (11) [Wed Jan 1 21:35:39 2003] [notice] child pid 14006 exit signal Segmentation fault (11) [Wed Jan 1 21:35:40 2003] [notice] child pid 13908 exit signal Segmentation fault (11) [Wed Jan 1 21:35:44 2003] [notice] child pid 14009 exit signal Segmentation fault (11) [Wed Jan 1 21:35:46 2003] [notice] child pid 13903 exit signal Segmentation fault (11) [Wed Jan 1 21:35:52 2003] [notice] child pid 14017 exit signal Segmentation fault (11) [Wed Jan 1 21:36:11 2003] [notice] child pid 14015 exit signal Segmentation fault (11) [Wed Jan 1 21:36:17 2003] [notice] child pid 14023 exit signal Segmentation fault (11) [Wed Jan 1 21:36:33 2003] [notice] child pid 14016 exit signal Segmentation fault (11) [Wed Jan 1 21:36:42 2003] [notice] child pid 14019 exit signal Segmentation fault (11) [Wed Jan 1 21:36:45 2003] [notice] child pid 14043 exit signal Segmentation fault (11) This is making me and my users _very_ unhappy :\ With 4.2.3 I got: (gdb) bt #0 0x42082a0c in memcpy () from /lib/i686/libc.so.6 #1 0x08134f7d in _estrndup () #2 0x0810deb0 in php_var_unserialize () #3 0x0810e796 in php_var_unserialize () #4 0x0810dd7a in php_var_unserialize () #5 0x08106dbc in zif_unserialize () #6 0x08169483 in execute () #7 0x08145b8e in zend_execute_scripts () #8 0x0808a06a in php_execute_script () #9 0x081511ca in apache_php_module_main () #10 0x0808638c in php_restore_umask () #11 0x080863e5 in php_restore_umask () #12 0x08173363 in ap_invoke_handler () #13 0x08187e9b in ap_some_auth_required () #14 0x08187efc in ap_process_request () #15 0x0817ef05 in ap_child_terminate () #16 0x0817f173 in ap_child_terminate () #17 0x0817f4f0 in ap_child_terminate () #18 0x0817fac5 in ap_child_terminate () #19 0x081800ff in main () #20 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 But with 4.3.0 I get: (gdb) bt #0 0x4204a646 in canonicalize () from /lib/i686/libc.so.6 #1 0x08182ced in virtual_file_ex () #2 0x08093ba0 in expand_filepath () #3 0x08092d30 in php_check_specific_open_basedir () #4 0x08092f12 in php_check_open_basedir () #5 0x0809c303 in _php_stream_fopen_with_path () #6 0x0809d243 in php_unregister_url_stream_wrapper () #7 0x0809d94d in _php_stream_open_wrapper_ex () #8 0x0809dc3b in _php_stream_open_wrapper_as_file () #9 0x0809010e in zif_set_time_limit () #10 0x080a2573 in open_file_for_scanning () #11 0x080a26f7 in compile_file () #12 0x080a2898 in compile_filename () #13 0x080cc601 in execute () #14 0x080ca99a in execute () #15 0
#14365 [Com]: require_once() causes segfault
ID: 14365 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: iPlanet related Operating System: RedHat Linux 7.3 PHP Version: 4.3.0-dev New Comment: I would love to but I don't have a clue how I should do that :D I'm using Apache 1.3.26 and PHP 4.3.0 (but that one segfaults too often) and PHP 4.2.3 (segfaults too but less often, especially when we use a debug build and limit the MaxRequestsPerChild to 10. Nested evals()? Hmm, we shouldn't, I'll go and see if that can be the case. BTW how did Sean create that backtrace? It even shows in what PHP file and on what line Apache/PHP went down... Previous Comments: [2003-01-02 11:54:51] [EMAIL PROTECTED] Can you try increasing your stack size as was suggested in one of the earlier responses? The latest backtrace looks *very* deep - are you using a lot of nested eval() calls ? [2003-01-01 14:55:40] [EMAIL PROTECTED] Oh, sorry. Forgot to mention what the site is running on. We're using Apache 1.3.26 with PHP as a module. Info page is over here: http://www.bokt.nl/klad/info.php It's a Redhat 7.3 box with: gcc version 2.96 2731 (Red Hat Linux 7.3 2.96-112) It's an Athlon 1800 XP with 1GB ram and phpBB is using MySQL (MyISAM tables) extensively. Some stats can be seen on: http://www.bokt.nl/stats/ [2003-01-01 14:51:48] [EMAIL PROTECTED] Grr. These damn segfaults are really driving me nuts. I've been having segfaults with other versions of PHP (up to 4.2.3). I'm using PHP 4.3.0 at the moment and the number of segfaults has only increased. Sometimes there are almost no segfaults (one every 5 minutes?) but sometimes I get stuff like this in the errorlog: [Wed Jan 1 21:34:02 2003] [notice] child pid 13840 exit signal Segmentation fault (11) [Wed Jan 1 21:34:03 2003] [notice] child pid 13833 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13831 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13816 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13810 exit signal Segmentation fault (11) [Wed Jan 1 21:34:20 2003] [notice] child pid 13837 exit signal Segmentation fault (11) [Wed Jan 1 21:34:45 2003] [notice] child pid 13883 exit signal Segmentation fault (11) [Wed Jan 1 21:34:50 2003] [notice] child pid 13878 exit signal Segmentation fault (11) [Wed Jan 1 21:34:51 2003] [notice] child pid 13887 exit signal Segmentation fault (11) [Wed Jan 1 21:34:51 2003] [notice] child pid 13859 exit signal Segmentation fault (11) [Wed Jan 1 21:34:52 2003] [notice] child pid 13882 exit signal Segmentation fault (11) [Wed Jan 1 21:35:24 2003] [notice] child pid 13904 exit signal Segmentation fault (11) [Wed Jan 1 21:35:31 2003] [notice] child pid 13898 exit signal Segmentation fault (11) [Wed Jan 1 21:35:31 2003] [notice] child pid 13892 exit signal Segmentation fault (11) [Wed Jan 1 21:35:36 2003] [notice] child pid 13909 exit signal Segmentation fault (11) [Wed Jan 1 21:35:39 2003] [notice] child pid 14006 exit signal Segmentation fault (11) [Wed Jan 1 21:35:40 2003] [notice] child pid 13908 exit signal Segmentation fault (11) [Wed Jan 1 21:35:44 2003] [notice] child pid 14009 exit signal Segmentation fault (11) [Wed Jan 1 21:35:46 2003] [notice] child pid 13903 exit signal Segmentation fault (11) [Wed Jan 1 21:35:52 2003] [notice] child pid 14017 exit signal Segmentation fault (11) [Wed Jan 1 21:36:11 2003] [notice] child pid 14015 exit signal Segmentation fault (11) [Wed Jan 1 21:36:17 2003] [notice] child pid 14023 exit signal Segmentation fault (11) [Wed Jan 1 21:36:33 2003] [notice] child pid 14016 exit signal Segmentation fault (11) [Wed Jan 1 21:36:42 2003] [notice] child pid 14019 exit signal Segmentation fault (11) [Wed Jan 1 21:36:45 2003] [notice] child pid 14043 exit signal Segmentation fault (11) This is making me and my users _very_ unhappy :\ With 4.2.3 I got: (gdb) bt #0 0x42082a0c in memcpy () from /lib/i686/libc.so.6 #1 0x08134f7d in _estrndup () #2 0x0810deb0 in php_var_unserialize () #3 0x0810e796 in php_var_unserialize () #4 0x0810dd7a in php_var_unserialize () #5 0x08106dbc in zif_unserialize () #6 0x08169483 in execute () #7 0x08145b8e in zend_execute_scripts () #8 0x0808a06a in php_execute_script () #9 0x081511ca in apache_php_module_main () #10 0x0808638c in php_restore_umask () #11 0x080863e5 in php_restore_umask () #12 0x08173363 in ap_invoke_handler () #13 0x08187e9b in ap_some_auth_required () #14 0x08187efc in ap_process_request () #15 0x0817ef05 in ap_child_terminate () #16 0x0817f173 in ap_child_terminate () #17 0x0817f4f0 in ap_
#14365 [Com]: require_once() causes segfault
ID: 14365 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: iPlanet related Operating System: RedHat Linux 7.3 PHP Version: 4.3.0-dev New Comment: I've read the backtrace page but the bt there doesn't show php filenames and linenumber.. But Sean mailed me that I should try 'bt full', I'll try that the next time. Anyway, as I said I'm using Apache and not iPlanet... The canonicalize problem only seems to occur on 4.3.0, PHP 4.2.3 seems to segfault on memcopy() Previous Comments: [2003-01-05 09:33:15] [EMAIL PROTECTED] See http://bugs.php.net/bugs-generating-backtrace.php for details on making backtraces. The stack size appears to be a setting in the iPlanet configuration:Try modifying your ns/threads section to include a larger stacksize...the default one is 128*1024I ran into a stacksize problem on the recent redhat update (related to glibc) that was segfaulting on a dns lookup. I didn't associate it with the segfault I was getting for PHP (Including squirrelmail), but the segfault for SM is gone now for me after this fix and SM works perfectly. Try this sample: ns_section "ns/threads" ns_param stacksize [expr 256*1024] " (quoted from this bug report). I don't have and have never used iPlanet, so it's up to you to find out how to configure it. " [2003-01-05 09:07:05] [EMAIL PROTECTED] I would love to but I don't have a clue how I should do that :D I'm using Apache 1.3.26 and PHP 4.3.0 (but that one segfaults too often) and PHP 4.2.3 (segfaults too but less often, especially when we use a debug build and limit the MaxRequestsPerChild to 10. Nested evals()? Hmm, we shouldn't, I'll go and see if that can be the case. BTW how did Sean create that backtrace? It even shows in what PHP file and on what line Apache/PHP went down... [2003-01-02 11:54:51] [EMAIL PROTECTED] Can you try increasing your stack size as was suggested in one of the earlier responses? The latest backtrace looks *very* deep - are you using a lot of nested eval() calls ? [2003-01-01 14:55:40] [EMAIL PROTECTED] Oh, sorry. Forgot to mention what the site is running on. We're using Apache 1.3.26 with PHP as a module. Info page is over here: http://www.bokt.nl/klad/info.php It's a Redhat 7.3 box with: gcc version 2.96 2731 (Red Hat Linux 7.3 2.96-112) It's an Athlon 1800 XP with 1GB ram and phpBB is using MySQL (MyISAM tables) extensively. Some stats can be seen on: http://www.bokt.nl/stats/ [2003-01-01 14:51:48] [EMAIL PROTECTED] Grr. These damn segfaults are really driving me nuts. I've been having segfaults with other versions of PHP (up to 4.2.3). I'm using PHP 4.3.0 at the moment and the number of segfaults has only increased. Sometimes there are almost no segfaults (one every 5 minutes?) but sometimes I get stuff like this in the errorlog: [Wed Jan 1 21:34:02 2003] [notice] child pid 13840 exit signal Segmentation fault (11) [Wed Jan 1 21:34:03 2003] [notice] child pid 13833 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13831 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13816 exit signal Segmentation fault (11) [Wed Jan 1 21:34:11 2003] [notice] child pid 13810 exit signal Segmentation fault (11) [Wed Jan 1 21:34:20 2003] [notice] child pid 13837 exit signal Segmentation fault (11) [Wed Jan 1 21:34:45 2003] [notice] child pid 13883 exit signal Segmentation fault (11) [Wed Jan 1 21:34:50 2003] [notice] child pid 13878 exit signal Segmentation fault (11) [Wed Jan 1 21:34:51 2003] [notice] child pid 13887 exit signal Segmentation fault (11) [Wed Jan 1 21:34:51 2003] [notice] child pid 13859 exit signal Segmentation fault (11) [Wed Jan 1 21:34:52 2003] [notice] child pid 13882 exit signal Segmentation fault (11) [Wed Jan 1 21:35:24 2003] [notice] child pid 13904 exit signal Segmentation fault (11) [Wed Jan 1 21:35:31 2003] [notice] child pid 13898 exit signal Segmentation fault (11) [Wed Jan 1 21:35:31 2003] [notice] child pid 13892 exit signal Segmentation fault (11) [Wed Jan 1 21:35:36 2003] [notice] child pid 13909 exit signal Segmentation fault (11) [Wed Jan 1 21:35:39 2003] [notice] child pid 14006 exit signal Segmentation fault (11) [Wed Jan 1 21:35:40 2003] [notice] child pid 13908 exit signal Segmentation fault (11) [Wed Jan 1 21:35:44 2003] [notice] child pid 14009 exit signal Segmentation fault (11) [Wed Jan 1 21:35:46 2003] [notice] child pid 13903 exit signal Segmentation fault (11)
#14365 [Com]: require_once() causes segfault
ID: 14365 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: iPlanet related Operating System: RedHat Linux 7.3 PHP Version: 4.3.0-dev New Comment: We are using evals but the worst I could find was 65 evals on one page (the template system uses evals for nested blocks). The index page has a complex template and needs 55 evals, normal pages only need 4 or 5 evals. Previous Comments: [2003-01-06 01:58:31] [EMAIL PROTECTED] I've read the backtrace page but the bt there doesn't show php filenames and linenumber.. But Sean mailed me that I should try 'bt full', I'll try that the next time. Anyway, as I said I'm using Apache and not iPlanet... The canonicalize problem only seems to occur on 4.3.0, PHP 4.2.3 seems to segfault on memcopy() [2003-01-05 09:33:15] [EMAIL PROTECTED] See http://bugs.php.net/bugs-generating-backtrace.php for details on making backtraces. The stack size appears to be a setting in the iPlanet configuration:Try modifying your ns/threads section to include a larger stacksize...the default one is 128*1024I ran into a stacksize problem on the recent redhat update (related to glibc) that was segfaulting on a dns lookup. I didn't associate it with the segfault I was getting for PHP (Including squirrelmail), but the segfault for SM is gone now for me after this fix and SM works perfectly. Try this sample: ns_section "ns/threads" ns_param stacksize [expr 256*1024] " (quoted from this bug report). I don't have and have never used iPlanet, so it's up to you to find out how to configure it. " [2003-01-05 09:07:05] [EMAIL PROTECTED] I would love to but I don't have a clue how I should do that :D I'm using Apache 1.3.26 and PHP 4.3.0 (but that one segfaults too often) and PHP 4.2.3 (segfaults too but less often, especially when we use a debug build and limit the MaxRequestsPerChild to 10. Nested evals()? Hmm, we shouldn't, I'll go and see if that can be the case. BTW how did Sean create that backtrace? It even shows in what PHP file and on what line Apache/PHP went down... [2003-01-02 11:54:51] [EMAIL PROTECTED] Can you try increasing your stack size as was suggested in one of the earlier responses? The latest backtrace looks *very* deep - are you using a lot of nested eval() calls ? [2003-01-01 14:55:40] [EMAIL PROTECTED] Oh, sorry. Forgot to mention what the site is running on. We're using Apache 1.3.26 with PHP as a module. Info page is over here: http://www.bokt.nl/klad/info.php It's a Redhat 7.3 box with: gcc version 2.96 2731 (Red Hat Linux 7.3 2.96-112) It's an Athlon 1800 XP with 1GB ram and phpBB is using MySQL (MyISAM tables) extensively. Some stats can be seen on: http://www.bokt.nl/stats/ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/14365 -- Edit this bug report at http://bugs.php.net/?id=14365&edit=1
