Re: segmentation fault - core dump

It pretty much means that something has so scrambled the "brains" of the computer that it just ups and dies. Well, actually, in the case of Un*x, it means that *PROCESS* dies. If this were Windows, it would be a "General Protection Fault". But it's not Windows. The "brains" are all compartmentalized in Un*x so that one program can't bring the whole machine down. (Well, in theory...) In an ideal world, there would be *NOTHING* you could type in PHP that would cause a segfault. (Not counting exec et al that would run some program not under PHP's control.) For more info on how to deal with the core dump, see: http://bugs.php.net When these programs puke, they also leave a big pile of vomit in a file named "core" that can be examined by experts to find out what was in the stomach of the computer at that time. -- WARNING richard@zend.com address is an endangered species -- Use ceo@l-i-e.com Wanna help me out? Like Music? Buy a CD: http://l-i-e.com/artists.htm Volunteer a little time: http://chatmusic.com/volunteer.htm ----- Original Message ----- From: Jack Dempsey <dempsejn@georgetown.edu> Newsgroups: php.general To: PHP General List <php-general@lists.php.net> Sent: Thursday, September 13, 2001 1:35 AM Subject: segmentation fault - core dump > hi all, > > could someone give me a description of what this really means? i know what > it means in general, but in php, what are the likely candidates? i thougth i > had it narrowed down to a warning in fopen and a bad fp, but i've taken care > of that, and its still core dumping...i'm using the cgi version, it didn't > seem to have this problem when accessed via teh web & apache...there's too > much code to really include, so anyone who has a second and some thoughts on > how this most likely occurs, your thoughts would be much appreciated.... > thanks, > jack >