|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #27830 PHP segfaults immediately on startup
Submitted: 2004-04-01 23:00 UTC Modified: 2004-12-23 01:00 UTC
Avg. Score:4.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: adconrad at 0c3 dot net Assigned:
Status: No Feedback Package: Reproducible crash
PHP Version: 4.3.7 OS: Debian 3.0/SPARC
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2004-04-01 23:00 UTC] adconrad at 0c3 dot net
PHP segfaults immediately on execution, with or without input on SPARC.  If the patch[1] applied in CVS (ostensibly to "improve portability") is removed, the segfault goes away.

1. A short script that reproduces the problem.

adconrad@cranx:~/build/php4/php-4.3.6RC1$ sapi/cli/php
Segmentation fault
2. The list of modules you compiled PHP with (your configure line). 

'./configure' '--disable-all' '--prefix=/usr/local/php-4.3.6RC1' '--with-apxs2=/usr/bin/apxs2' '--enable-sockets' '--with-pcre-regex' '--enable-ctype' '--enable-overload' '--enable-posix' '--enable-session' '--enable-tokenizer' '--enable-xml' '--with-expat-dir=/usr' '--with-xmlrpc' '--with-pear' '--with-openssl' '--with-mysql=shared,/usr' '--with-pgsql=shared,/usr' '--with-sybase-ct=shared,/usr/local/freetds'

3. Any other information unique or specific to your setup. 

Debian GNU/Linux 3.0 (woody), SPARC port on an UltraSPARC (sparc64) CPU.  glibc version 2.2.5-11.5.

4. Any changes made in your php.ini compared to php.ini-dist (not your whole php.ini!) 

This occurs with or without a php.ini.

5. A gdb backtrace.

Program received signal SIGSEGV, Segmentation fault.
0x0005e170 in php_get_inf ()
    at /home/adconrad/build/php4/php-4.3.6RC1/ext/standard/basic_functions.c:1021
1021            return HUGE_VAL;
(gdb) bt
#0  0x0005e170 in php_get_inf ()
    at /home/adconrad/build/php4/php-4.3.6RC1/ext/standard/basic_functions.c:1021
#1  0x0005e4d4 in zm_startup_basic (type=1, module_number=4)
    at /home/adconrad/build/php4/php-4.3.6RC1/ext/standard/basic_functions.c:1065
#2  0x000ef068 in zend_startup_module (module=0x14647c)
    at /home/adconrad/build/php4/php-4.3.6RC1/Zend/zend_API.c:1005
#3  0x000bead0 in php_startup_extensions (ptr=0x14eabc, count=1370840)
    at /home/adconrad/build/php4/php-4.3.6RC1/main/main.c:1044
#4  0x00108334 in php_startup_internal_extensions () at main/internal_functions_cli.c:65
#5  0x000bf0b8 in php_module_startup (sf=0x149570, additional_modules=0x0,
    num_additional_modules=0) at /home/adconrad/build/php4/php-4.3.6RC1/main/main.c:1216
#6  0x001074c8 in main (argc=1, argv=0xeffffb34)
    at /home/adconrad/build/php4/php-4.3.6RC1/sapi/cli/php_cli.c:576



Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2004-04-02 04:41 UTC]
Could you post your compiler version and the output of 
'configure' ? 
 [2004-04-02 08:57 UTC] adconrad at 0c3 dot net
adconrad@cranx:~$ gcc -v
Reading specs from /usr/lib/gcc-lib/sparc-linux/2.95.4/specs
gcc version 2.95.4 20011002 (Debian prerelease)

./configure output (and log) is at{out,log}
 [2004-04-02 17:19 UTC]
Could you try and compile with gcc-3.3 ? (I'm not 
suggesting this as a fix, I'm just curious if it will work 
around the problem)  
I would do it myself if I had access to a Sparc64/linux 
 [2004-04-02 18:52 UTC] 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.
 [2004-04-02 19:44 UTC] 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-03 06:42 UTC] adconrad at 0c3 dot net
The latest snapshot didn't actually have any changes other than derick's valgrind-induced fixes, and still failed.  Of course, this is what I get for responding too quickly to the bug.  :)

I snagged your config.m4 changes from CVS, applied them, regenerated configure, and the resulting binary still segfaults with the same backtrace as before.

config.{out,log} and build.log available at the same URL as always, with a "gcc-2.95-snapshot" suffix.
 [2004-04-03 07:29 UTC]
Please try using this CVS snapshot:
For Windows:

Please try the new config.m4 
Could you try and tweak the #ifdefs if they still don't 
work, and report back here. 
Clearly, this is a compiler/glibc bug. Sounds like 
something you guys at Debian might wanna fix as well. 
 [2004-04-03 08:31 UTC] adconrad at 0c3 dot net
> Please try the new config.m4 

No go.  The glibc tests appear to be incorrect.  I took them out anyway, and changed the others, as rationalised below.

> Could you try and tweak the #ifdefs if they still don't 
> work, and report back here. 

New and improved line:
#if (__GNUC__ == 2)&&(__GNUC_MINOR <= 96)&&defined(__sparc__)

1. I bumped the __GNUC_MINOR version to 96, as I will give you 99-to-1 odds the bug lasted until later pre-releases, and there are a couple of dists out there (*cough*RedHat*cough*) that actually released a stable dist based on that buggy pre-release.  I can't verify this in the GCC bug tracker right now, but given how few people would be running gcc-2.96 on SPARC, I'd say it's a "better safe than dealing with a duplicate bug that no one can hunt down later" thing.

2. I pulled out the glibc check after confirming that building with gcc-2.95 on a system with glibc 2.3 produces the same segfaulting binary.  It's all GCC's fault, glibc is an innocent bystander.

3. I changed __sparc64 (a define that doesn't always (or ever, in some systems) exist to __sparc__, since while I reported this happening on a sparc64 system, one must realise that sparc64 systems are sparc32 in user-space (well, most of them are).  Compiling for sparc32 or sparc64 targets produces the same bug, so a generic __sparc__ test seems to make more sense.

With this new and improved line, the Ugly Hack(tm) to work around this compiler issue seems to work just fine.  Thanks for the help hunting it down and giving it some TLC.

> Clearly, this is a compiler/glibc bug. Sounds like 
> something you guys at Debian might wanna fix as well. 

Certainly looks like a GCC bug, yes.  However, it's a GCC bug in our stable release (which doesn't get compiler updates, or PHP updates for that matter, with the exception of security fixes), so it's not going to get fixed (this problem doesn't show up in sarge (our upcoming stable release) or sid (unstable)).  Doesn't stop me from trying to run the latest PHP on production machines running Debian/stable, however. :)

I'm not sure how many other Debian/SPARC users try to use the latest PHP on stable systems, but I'm sure they'd thank you for your efforts.  Most probably use the php4 packages provided by Debian (and packaged by me, ironically) that work just fine, but there's always a few build-from-source types out there.
 [2004-04-03 08:34 UTC] adconrad at 0c3 dot net
As an added note, I didn't bother trying to add a glibc or linux test in there, as most arch-specific compiler bugs seem to span OSs, and this bug would probably affect Solaris as well.  We don't have a Solaris machine in-house anymore for me to test this theory on, however.
 [2004-04-04 06:14 UTC]
This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
Thank you for the report, and for helping us make PHP better.
 [2004-06-07 05:14 UTC] adconrad at 0c3 dot net
This bug has returned in PHP 4.3.7 with the changes made in ext/standard/config.m4, rev
 [2004-12-14 08:53 UTC] adconrad at 0c3 dot net
I don't have a Sparc machine in front of me right now to test, but looking at CVS, I don't see HOW this can be fixed, as the relevant portions of config.m4 haven't been touched since I reopened the bug.
 [2004-12-15 01:33 UTC]
If you have fixes, provide a patch.
 [2004-12-23 01:00 UTC] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Wed Nov 29 19:01:27 2023 UTC