ID: 47441
User updated by: jpilling at fortvale dot com
Reported By: jpilling at fortvale dot com
Status: Open
Bug Type: Compile Failure
Operating System: zLinux - SLES 10 s390x 64bit
PHP Version: 5.3.0beta1
New Comment:
Ok, I understand how to get the backtrace now, but the segmentation
fault on "make test" will only occur if I --disable-debug, so how can I
get a backtrace if debugging is not enabled? If I use --enable-debug php
compiles OK.
I ran GDB anyway after my compile with --disable-debug, which is
probably useless, and i got:
(gdb) run /home/php-5.3.0beta1/run-tests.php
Starting program: /home/php-5.3.0beta1/sapi/cli/php
/home/php-5.3.0beta1/run-tests.php
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 2199031317472 (LWP 9045)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 2199031317472 (LWP 9045)]
0x000000008027ea22 in ?? ()
Previous Comments:
------------------------------------------------------------------------
[2009-02-20 08:19:14] jpilling at fortvale dot com
I tried the following to generate the backtrace (i'm not 100% sure if
I'm doing the right thing, sorry ):
TEST_PHP_EXECUTABLE=/home/php-5.3.0beta1/sapi/cli/php gdb
Once GDB starts to run I enter:
run /home/php-5.3.0beta1/run-tests.php
The output is:
Starting program: /home/php-5.2.8/run-tests.php
No executable file specified.
Use the "file" or "exec-file" command.
------------------------------------------------------------------------
[2009-02-19 22:51:54] jpilling at fortvale dot com
Sorry, I don't know which is a PHP fault or which is an Apache fault.
I don't know how to create a backtrace. I read the instructions but i'm
struggling to understand. It mentions a script that causes the
crash....is that the run-tests.php script?
Do I need to run the home/php5.3.0beta1/sapi/cli/php executable using
gdb, and run the test script to get a backtrace?
If thats correct, I get the error that /home/php5.3.0beta1/sapi/cli/php
is not an executable when trying to run it with gdb.
Any ideas?
Sorry for my inexperience.
------------------------------------------------------------------------
[2009-02-19 21:44:22] j...@php.net
Oh, and we still don't have the backtrace of the bug you originally
reported..
------------------------------------------------------------------------
[2009-02-19 21:43:53] j...@php.net
I didn't say the ORIGINAL issue wasn't a PHP bug. Please don't post
irrelevant stuff or multiple bugs in one report.
------------------------------------------------------------------------
[2009-02-19 15:35:16] jpilling at fortvale dot com
The bottom line is that if I try to compile PHP as an apache module OR
as Fast-CGI - the "make test" fails with a segmentation fault unless
--enable-debug is present in my configure line, and -liconv and -glibc
are present in the EXTRA_LIBS part of my makefile.
I've been testing this for months now. So how is this NOT a PHP bug?
------------------------------------------------------------------------
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/47441
--
Edit this bug report at http://bugs.php.net/?id=47441&edit=1
