ID:               42893
 User updated by:  hoffie at gentoo dot org
 Reported By:      hoffie at gentoo dot org
-Status:           No Feedback
+Status:           Open
 Bug Type:         Reproducible crash
 Operating System: Linux on ia64
-PHP Version:      5CVS-2007-10-08 (snap)
+PHP Version:      5.2.5RC2
 New Comment:

Yes, I admit that above gdb output shows some strangeness, but well --
that's a gdb problem, not generally software being broken on that
system. Upgrading gdb resolved that problem and here goes the new
backtrace (using 5.2.5RC2 now):

(gdb) r -n -r 'var_dump(defined("foo"));'

Starting program: /tmp/php-5.2.5RC2/sapi/cli/php -n -r
'var_dump(defined("foo"));'

Program received signal SIGSEGV, Segmentation fault.
_zval_ptr_dtor (zval_ptr=0x60000ffffff3ebd0)
    at /tmp/php-5.2.5RC2/Zend/zend_execute_API.c:412
412             (*zval_ptr)->refcount--;
(gdb) bt
#0  _zval_ptr_dtor (zval_ptr=0x60000ffffff3ebd0)
    at /tmp/php-5.2.5RC2/Zend/zend_execute_API.c:412
#1  0x4000000000298a80 in zend_do_fcall_common_helper_SPEC (
    execute_data=0x60000ffffff3ec50)
    at /tmp/php-5.2.5RC2/Zend/zend_execute.h:155
#2  0x4000000000297200 in execute (op_array=0x60000000000c86e0)
    at /tmp/php-5.2.5RC2/Zend/zend_vm_execute.h:92
#3  0x4000000000228800 in zend_eval_string (str=<value optimized out>,

    retval_ptr=0x0, string_name=0x400000000041fd10 "Command line
code")
    at /tmp/php-5.2.5RC2/Zend/zend_execute_API.c:1171
#4  0x4000000000228c10 in zend_eval_string_ex (
    str=0x60000ffffff3f740 "var_dump(defined(\"foo\"));",
retval_ptr=0x0, 
    string_name=0x400000000041fd10 "Command line code",
handle_exceptions=1)
    at /tmp/php-5.2.5RC2/Zend/zend_execute_API.c:1205
#5  0x40000000003a2130 in main (argc=Cannot access memory at address
0x10
)
    at /tmp/php-5.2.5RC2/sapi/cli/php_cli.c:1179


Previous Comments:
------------------------------------------------------------------------

[2007-11-08 15:02:52] mail at markus-ullmann dot de

erm...

[29 Oct 11:15pm UTC] [EMAIL PROTECTED] 
Not only PHP breaks but also GDB.

Tell me plz how you guessed that GDB is broken. Just valgrind is not 
available on ia64 architecture but gdb works fine.

[8 Oct 7:24pm UTC] hoffie at gentoo dot org
As soon as debugging symbols are enabled (CFLAGS=-g or
./configure --enable-debug) the problem disappears, that's why I'm
unable to provide a useful backtrace.

Notice that the _problem disappears_.

------------------------------------------------------------------------

[2007-11-06 01:00:01] 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".

------------------------------------------------------------------------

[2007-10-29 23:15:46] [EMAIL PROTECTED]

>From the looks of it, you have more problems than just PHP here. Not
only PHP breaks but also GDB. How about you try get the basic tools
working before trying PHP? :)

------------------------------------------------------------------------

[2007-10-13 10:13:40] hoffie at gentoo dot org

> Just to be sure you're not loading any php.ini files, try this:
> (gdb) run -n -r 'var_dump(defined("foo"));'
Fails with the same symptoms.

> And you could also try to see what valgrind has to say about it:
> # USE_ZEND_ALLOC=0 valgrind --leak-check=yes php -n -r
> 'var_dump(defined("foo"));'
If you gave me valgrind for ia64 I'd happily do that. ;)

> checking for a supported CPU... no (ia64)
> configure: error: Unsupported host architecture. Sorry

------------------------------------------------------------------------

[2007-10-11 13:46:28] [EMAIL PROTECTED]

Just to be sure you're not loading any php.ini files, try this:

(gdb) run -n -r 'var_dump(defined("foo"));'

And you could also try to see what valgrind has to say about it:

# USE_ZEND_ALLOC=0 valgrind --leak-check=yes php -n -r
'var_dump(defined("foo"));'


------------------------------------------------------------------------

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/42893

-- 
Edit this bug report at http://bugs.php.net/?id=42893&edit=1

Reply via email to