#27830 [Fbk->Opn]: PHP segfaults immediately on startup

ID: 27830 User updated by: adconrad at 0c3 dot net Reported By: adconrad at 0c3 dot net -Status: Feedback +Status: Open Bug Type: Reproducible crash Operating System: Debian 3.0/SPARC PHP Version: 4.3.6RC1 New Comment: helly: Which "unstable" system is that? As I mentioned, it's Debian stable, with what was at the time considered to be the most stable and sane compiler. abies: I'll give it a whirl right now. I assume by the "rerun buildconf" comment that it's just a change to detect this particular compiler bug? I'll check and see how it works. Previous Comments: ------------------------------------------------------------------------ [2004-04-03 04:38:12] abies@php.net ... and be sure to re-run buildconf ------------------------------------------------------------------------ [2004-04-03 04:37:57] helly@php.net Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Thank you for your interest in PHP. In this case the error obviously comes from the unstable system you\'re using. It would be a very good idea to tell the developers of all unstable things you were using about the problem: returning a double shouldn\'t fail at all. ------------------------------------------------------------------------ [2004-04-03 04:37:43] abies@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip ------------------------------------------------------------------------ [2004-04-02 19:44:34] adconrad at 0c3 dot net Okay, there isn't much point in testing with gcc-3.3 on an unstable system. I just install gcc-3.0.4 on the same stable system I was testing this bug on, and it seems to work just fine. config.{out,log}-gcc-3.0 and build.log-gcc-3.0 at the same URL as previous logs. So, to repeat: This bug appears to vanish building with gcc-3.0.4 (and presumably any gcc 3.x), but manifests with gcc-2.95. ------------------------------------------------------------------------ [2004-04-02 18:52:11] adconrad at 0c3 dot net I'll build a Debian unstable chroot with gcc-3.3 and give it a whirl. Of course, that'll also be using a new glibc, among other things, so it's not terribly scientific. I could also try gcc-3.0 on a stable system and see if that makes it happy. Either way, gcc-2.95 and glibc 2.2 is a combination that should probably be on the supported list for a while yet, I'd say. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/27830 -- Edit this bug report at http://bugs.php.net/?id=27830&edit=1