What causes "Abort (core dumped)"?
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this?Here's a link to a previous thread I started a long time ago on this:
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based)rted a long time ago on this:
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated commrk.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my tp://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly resurface on my hosted site. Here's a link to a previous thread I started a long time ago on this:
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpmp;lt;?php
echo "Why does this dump core?";
?>
Output is:
Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this?ve tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-larted a long time ago on this:
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated link to a previous thread I started a long time ago on this:
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script aing this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this? from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can cong the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this?this dump core?Abort (core dumped)
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this? quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).m persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core filecc]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
Output is:
Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at le resurface on my hosted site. Here's a link to a previous thread I started a long time ago on this:
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I hae gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this? Here's a link to a previous thread I started a long time ago on this:
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directlyder has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this?e. Here's a link to a previous thread I started a long time ago on this:
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local ep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control ovelate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this?y hosted site. Here's a link to a previous thread I started a long time ago on this:
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this? suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
Code: Select all
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>Code: Select all
> ./test.php
Why does this dump core?Abort (core dumped resurface on my hosted site. Here's a link to a previous thread I started a long time ago on this:
http://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/htthis for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at lprevious thread I started a long time ago on this:
http://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose thisng provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this? resurface on my hosted site. Here's a link to a previous thread I started a long time ago on this:
http://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configur has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "returp?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machinesn/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear ions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this?sting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this? resurface on my hosted site. Here's a link to a previous thread I started a long time ago on this:
http://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I cad I started a long time ago on this:
http://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated website. Here's a link to a previous thread I started a long time ago on this:
http://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this? to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerat
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its //forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more Here's a link to a previous thread I started a long time ago on this:
http://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux basong time ago on this:
http://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su to root and have control over php.ini/httpd.conf directly, etc. Any ideas about how I can continue to diagnose this?d (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is r tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't work.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in caseing provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere ago on this:
http://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.
The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages appear to work fine (at least I haven't found any core files stashed anywhere else on my server). The more complicated command-line scripts work fine on either of my local development machines (Mac OS X or Debian Linux based).
While its a shared server, it configured as a "virtual machine"; I can su tp://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)
[/code]
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is wanting an explicit "successful program termination" signal, but it still fails in the same manner.hread I started a long time ago on this:
http://forums.devnetwork.net/viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" notices from them, but the problem persists. I'ld like to try to help them figure out what's the real problem.
I've tried following the suggestions in the previous thread (ie use gdb to isolate the command issuing the abort), but doing so causes gdb to dump core as well.
My current test script is simply
[php]
#!/usr/local/bin/php
<?php
echo "Why does this dump core?";
?>
[/php]
Output is:
[code]
> ./test.php
Why does this dump core?Abort (core dumped)The server is running on FreeBSD, and appears to be using one of the various script accelerators, "eaccelerator". PHP generated web-pages apnk to a previous thread I started a long time ago on this:
viewtopic.php?t=27236
The hosting provider has been fighting this for quite some time. I keep getting "fixed" not