[xdebug-general] Re: xdebug stack traces doesn't work

On Thu, 17 Jun 2004, [iso-8859-1] Ronny Riedel wrote:

> > Please create a backtrace as described here:
> > http://bugs.php.net/bugs-generating-backtrace.php
>
> the output:
>
> #0 0x0000002a963dbd88 in chunk_alloc () from /lib64/libc.so.6
> #1 0x0000002a963dbbc1 in malloc () from /lib64/libc.so.6
> #2 0x0000002a97c062aa in xdebug_llist_insert_next (l=0x4032ec20, e=0x0, p=0x4032ec50)
> at /[...]/source/xdebug/xdebug-from-cvs/xdebug_llist.c:53
> #3 0x0000002a97bfc26d in add_stack_frame (zdata=0x0, op_array=0x2a95590658, type=-1747887232)
> at /[...]/source/xdebug/xdebug-from-cvs/xdebug.c:772
> #4 0x0000002a97bfc880 in xdebug_execute (op_array=0x2a95590658)
> at /[...]/source/xdebug/xdebug-from-cvs/xdebug.c:958
> #5 0x0000002a96711449 in zend_execute_scripts (type=8, retval=0x0, file_count=3)
> at /[...]/source/php/php-5.0.0RC3/Zend/zend.c:1061
> #6 0x0000002a966de987 in php_execute_script (primary_file=0x7fbfffe8a0)
> at /[...]/source/php/php-5.0.0RC3/main/main.c:1627

This definitely sounds like a 64 bit problem to me. Did you have any
warnings compiling Xdebug? And does it happen will all scripts? If so,
can you provide me with a sample?

Especially type=-1747887232 (fraome #3) is weird, it can only be 1 or 2
so I've no idea where this comes from.

regards,
Derick
Received on Fri Jun 18 2004 - 09:17:47 BST