When you have a process running in System Memory and it does not finish, the portion of memory that the process was using is dumped to a file for further reivew. This is helpful for debugging your scripts. Core dumps usually have a file name that looks similar to:
core.5744
For the average user (and even the advanced user), getting information out of a core dump can be difficult. Most of the information contained in core dumps can be found with either of the two commands:
gdb -c core.####
strings core.####
These commands above need to be ran from the command line, however most shared hosting (including Web Hosting Hub) does not allow command line access for security reasons. We've created a simple php script that allows you to find core dumps and use the commands above to review their contents. The script can be found here:
http://www.webhostinghub.com/support/files/scripts/coredumpcheck.txt
Look under the "RUNNING: gdb -c core.30387" heading to find the script that is causing the problem. It will be in a line that looks similar to:
We've highlighted the correct line in the screenshot below.
Core Dumps in nature are an advanced topic. It is best to contact your website developer with the information that you have obtained using the coredumpcheck.php file.
Email: | support@WebHostingHub.com | Ticket: | Submit a Support Ticket |
---|---|---|---|
Call: |
877-595-4HUB (4482) 757-416-6627 (Intl.) |
Chat: | Click To Chat Now |
We value your feedback!
There is a step or detail missing from the instructions.
The information is incorrect or out-of-date.
It does not resolve the question/problem I have.
new! - Enter your name and email address above and we will post your feedback in the comments on this page!