[xdebug-dev] Bug 0000028: xdebug_llist_init (l=0x0, dtor=0x190b7d6c <hash_element_dtor>)

The following bug has been RESOLVED.
======================================================================
http://bugs.xdebug.org/bug_view_page.php?bug_id=0000028
======================================================================
Reporter: melvyn
Handler: derick
======================================================================
Project: Xdebug
Bug ID: 28
Category: Usage problems
Reproducibility: always
Severity: crash
Priority: normal
Status: resolved
Operating System: FreeBSD ghost.lan.webteckies.org 4.9-RC FreeBSD 4.9-RC http://bugs.xdebug.org/bug_view_page.php?bug_id=0000006: Wed Oct 1 07:44:36 CEST 2003 root@ghost.lan.webteckies.org:/usr/obj/usr/src/sys/GHOST i386
PHP Version: 4.3.4-dev
Xdebug Version: 1.3.0rc2
Resolution: unable to duplicate
======================================================================
Date Submitted: 2003-11-11 12:17 CET
Last Modified: 2004-09-15 10:08 CEST
======================================================================
Summary: xdebug_llist_init (l=0x0, dtor=0x190b7d6c <hash_element_dtor>)
Description:
Reproducable crash.
Requesting a 'Data Dictionary' on a database in phpMyAdmin 2.5.4 triggers
the bug. I currently have no time to further investigate the actual
trigger condition, but demonstrative patch is below
======================================================================

----------------------------------------------------------------------
 derick - 2003-12-01 15:44 CET
----------------------------------------------------------------------
I could not reproduce this with 4.3.5-dev, xdebug-2.0dev (current CVS) and
phpmyadm 2.5.4. Can you please tell me which xdebug related php.ini
settings you made and whether you have a debug or non-debug php build?

----------------------------------------------------------------------
 melvyn - 2003-12-02 01:28 CET
----------------------------------------------------------------------
Try --enable-memory-limit, default setting (8M) and a large enough number
of tables (in my case 41). I've screwed around with my php install in the
mean time.

Xdebug version above was used, but 1.2.0 was also affected.
I thought the bug would be clear from the patch, that the success of the
malloc was not checked. I found that backtracing.

AFAIR auto_trace and default_enable we're on. No phpdebug build.

----------------------------------------------------------------------
 melvyn - 2003-12-02 21:56 CET
----------------------------------------------------------------------
I'm pretty sure I've found the cause:
28094 www 2 0 320M 305M sbwait 0:09 10.27% 9.91% httpd

28126 www 2 0 22176K 14552K sbwait 0:07 25.31% 23.78% httpd

The first run is with 'autotrace' on. The second one, without. Apache was
stopped and started before the first run and in between the runs.

Both requested the data-dictionary of the same database. Since I've now
compiled php without memory limit, I do not hit the bug anymore but 300M
difference for autotrace seems to be a bit much - especially for a
webserver. If there is no bug here, then maybe autotrace should be
disabled when sapi != cli.

# php -i | grep xdebug
xdebug
xdebug support => enabled
xdebug.auto_profile => Off => Off
xdebug.auto_profile_mode => 0 => 0
xdebug.auto_trace => Off => Off
xdebug.collect_params => Off => Off
xdebug.default_enable => On => On
xdebug.dump.COOKIE => no value => no value
xdebug.dump.ENV => no value => no value
xdebug.dump.FILES => no value => no value
xdebug.dump.GET => no value => no value
xdebug.dump.POST => no value => no value
xdebug.dump.REQUEST => no value => no value
xdebug.dump.SERVER => no value => no value
xdebug.dump.SESSION => no value => no value
xdebug.dump_once => On => On
xdebug.dump_undefined => Off => Off
xdebug.manual_url => http://www.php.net => http://www.php.net
xdebug.max_nesting_level => 64 => 64
xdebug.output_dir => /tmp => /tmp
xdebug.remote_enable => Off => Off
xdebug.remote_handler => gdb => gdb
xdebug.remote_host => localhost => localhost
xdebug.remote_mode => req => req
xdebug.remote_port => 17869 => 17869

----------------------------------------------------------------------
 derick - 2004-09-15 10:08 CEST
----------------------------------------------------------------------
I'm going to mark this bug as resolved, as I'm still unable to duplicate
it. If you have more information about it, feel free to reopen it. Besides
that, the tracing in Xdebug 2.0 is much better anyway (and doesn't use much
memory at all!)

Derick

Bug History
Date Modified Username Field Change
======================================================================
2003-11-11 12:17melvyn New Bug
2003-12-01 15:44derick Bugnote Added: 0000067
2003-12-01 15:44derick Status new => feedback
2003-12-02 01:28melvyn Bugnote Added: 0000071
2003-12-02 21:56melvyn Bugnote Added: 0000072
2004-09-15 10:08derick Bugnote Added: 0000192
2004-09-15 10:08derick Assigned To => derick
2004-09-15 10:08derick Resolution open => unable to duplicate
2004-09-15 10:08derick Status feedback => resolved
======================================================================
Received on Wed Sep 15 2004 - 10:08:17 BST