Is dbug broken in 4.2.0RC4?

From: Date: Thu, 18 Apr 2002 02:15:14 +0000
Subject: Is dbug broken in 4.2.0RC4?
Groups: php.dev 
Request: Send a blank email to php-dev+get-82968@lists.php.net to get a copy of this message
Hi, I bumped to another segfault: #0 _db_return_ (_line_=1633, _sfunc_=0x1b4c1d8, _sfile_=0x1b4c1dc, _slevel_=0x1b4c1e0) at dbug.c:827 #1 0x006df19b in mysql_select_db (mysql=0x84454c8, db=0x87c52d8 "tft") at libmysql.c:1633 #2 0x006d9a4e in zif_mysql_select_db (ht=2, return_value=0x8628530, this_ptr=0x0, return_value_used=0, tsrm_ls=0x82e7680) at php_mysql.c:797 #3 0x00425258 in execute (op_array=0x87e0988, tsrm_ls=0x82e7680) at ./zend_execute.c:1598 #4 0x004278ec in execute (op_array=0x87cd980, tsrm_ls=0x82e7680) at ./zend_execute.c:2141 ... (gdb) frame 0 #0 _db_return_ (_line_=1633, _sfunc_=0x1b4c1d8, _sfile_=0x1b4c1dc, _slevel_=0x1b4c1e0) at dbug.c:827 827 state->framep = (char **) *state->framep; (gdb) print *state->framep Cannot access memory at address 0xa (gdb) print state->framep $7 = (char **) 0xa -- jul

Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
« previous php.dev (#82968) next »