What causes "Abort (core dumped)"?

PHP programming forum. Ask questions or help people concerning PHP code. Don't understand a function? Need help implementing a class? Don't understand a class? Here is where to ask. Remember to do your homework!

Moderator: General Moderators

Post Reply
User avatar
nielsene
DevNet Resident
Posts: 1834
Joined: Fri Aug 16, 2002 8:57 am
Location: Watertown, MA

What causes "Abort (core dumped)"?

Post by nielsene »

I've had a problem 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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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?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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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)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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does this dump core?Abort (core dumped)
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter 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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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/httpmp;lt;?php
echo "Why does this dump core?";
?>

Output is:

Code: Select all

> ./test.php
Why does 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?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?";
?>
Output is:

Code: Select all

> ./test.php
Why does this dump core?Abort (core dumped)
I've tried adding "exit(0)" or "return(0)". To the scripn 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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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.

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?";
?>
Output is:

Code: Select all

> ./test.php
Why does this dump core?Abort (core dumped)
I've tried adding "exit(0)" or "return(0)". To the script in case the interpreter is 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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? 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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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?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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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).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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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 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)
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 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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? 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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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?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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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 ts 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?";
?>
Output is:

Code: Select all

&gt; ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does this dump core?Abort (core dumped)
I've tried adding "exit(0)" 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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?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?";
?>
Output is:

Code: Select all

> ./test.php
Why does 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? 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?";
?>
Output is:

Code: Select all

> ./test.php
Why does this dump core?Abort (core dumped&#4 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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./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]
&gt; ./test.php
Why does 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 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
User avatar
s.dot
Tranquility In Moderation
Posts: 5001
Joined: Sun Feb 06, 2005 7:18 pm
Location: Indiana

Post by s.dot »

Most abort()'s I have seen are java related (perhaps to memory allocation problems?) I'm pretty positive it's a software problem on the host machine.

In any case, a good solid definition of the error message, can lead to the solution.

I found this.

http://docs.hp.com/en/B9106-90010/abort.3C.html

Sorry if that is not of much help.
User avatar
BDKR
DevNet Resident
Posts: 1207
Joined: Sat Jun 08, 2002 1:24 pm
Location: Florida
Contact:

Post by BDKR »

A core dump normally occurs when there is a crash. In this case, the PHP engine has crashed. What happens with a core dump is that memory associated is dumped out to a file. This helps in debugging.

I've had to deal with core dump issues in the past. It sucked! However, yours seems like it should be much simpler except for the fact that you are dealing with a web host. Tell them they need to recompile the damn thing. And try doing it this time without the accellerator.

Now you said FreeBSD right? Are they using the PORTS system to keep it up to date. I've seen an update (PHP in particular) come down the PORTS pipe and render the system useless.

Tell them to recompile.

I'm trying to remember the name of a program that you can run in conjunction with an executable (Windows need not apply here) that can provide a lot of output regarding the running program. If I do, I will post it here.

There is also Alicia. (Advanced LInux Crash-dump Interactive Analyzer)

Lastly, try running that script without the echo and see if it dumps. Can you run it from a command line?
User avatar
nielsene
DevNet Resident
Posts: 1834
Joined: Fri Aug 16, 2002 8:57 am
Location: Watertown, MA

Post by nielsene »

Without the echo ie just <?php ?> also core dumped.

The other linked thread mentioned gdb, the program I think you're referring to get to information about the crash -- it however also crashed on use.

The web-host just identified the interbase.so extension as apparently contributing to the problem. Its been commented out and now the cores have gone away.

It was always ONLY an error from the command-line, regular mod_php4 through apache was fine.

So it looks likes its fixed, now. Thanks.
User avatar
BDKR
DevNet Resident
Posts: 1207
Joined: Sat Jun 08, 2002 1:24 pm
Location: Florida
Contact:

Post by BDKR »

Cool!
Post Reply