Byron Posted August 26, 2008 Posted August 26, 2008 Attention djbob: Last night I found a very large (30.65 MB) core file inside one of my public directories: byrondallas.heliohost.org/php/tools/core.22338 so I thought I would leave it until this morning and see if it removed itself but I found it still there. So thinking it was just some server glitch I just went ahead and removed it. Then later this morning I was talking with a friend and this is what they told me: It happened once at my old TL/2 account and it had something to do with the server hard drive becoming corrupt. If I remember right I had core files only in each directory that had a shtml file in it. Don't have any idea if what happened to me has anything to do with what my friend told me but thought it a good idea to let you know. Byron
Ashoat Posted August 26, 2008 Posted August 26, 2008 That file is generated by PHP when it segfaults. It's probably a PHP bug. Have any of your PHP apps in that directory been crashing recently?
Byron Posted August 26, 2008 Author Posted August 26, 2008 That file is generated by PHP when it segfaults. It's probably a PHP bug. Have any of your PHP apps in that directory been crashing recently? Explain what you mean by "PHP apps". I recently made a couple of tools that use Imagick. One creates an image and annotates on that image with a true type font and the other just allows a person to view an off premise true type font. I was working on those tools over the weekend and doing allot of editing. I also sent those to a few friends of mne to use. More than likely those files would have been the culprit?
Ashoat Posted August 26, 2008 Posted August 26, 2008 If you still had the core file, I could do a backtrace which would probably explain some more specifics about the issue. Unfortunately, at this point it's impossible to determine what the bug was.
Byron Posted August 26, 2008 Author Posted August 26, 2008 If you still had the core file, I could do a backtrace which would probably explain some more specifics about the issue. Unfortunately, at this point it's impossible to determine what the bug was. My main concern was just making sure you knew about it and had an explanation for it. But knowing me it'll happen again in the future and next time I'll save it for you to check out. Thanks djbob! Regards, Byron
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now