#21890 [Opn->Fbk]: Segfault on mysql_fetch_object

From: Date: Mon, 10 Mar 2003 23:17:19 +0000
Subject: #21890 [Opn->Fbk]: Segfault on mysql_fetch_object
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-35304@lists.php.net to get a copy of this message
ID: 21890 Updated by: sniper@php.net Reported By: hans dot wolters at chello dot nl -Status: Open +Status: Feedback Bug Type: MySQL related Operating System: Linux kernel 2.4.20-pre5 PHP Version: 5CVS-2003-03-11 (dev) New Comment: Please add the full backtrace: (gdb) bt Previous Comments: ------------------------------------------------------------------------ [2003-03-10 17:04:16] hans dot wolters at chello dot nl Program received signal SIGSEGV, Segmentation fault. 0x4048e10f in zend_hash_exists (ht=0x406da808, arKey=0x264 <Address 0x264 out of bounds>, nKeyLength=1) at /home/software/php5/php5/Zend/zend_hash.c:923 923 HANDLE_NUMERIC(arKey, nKeyLength, zend_hash_index_exists(ht, idx)); I updated automake, autoconf and libtool to match the versions. Used the same configure options... Regards, Hans ------------------------------------------------------------------------ [2003-03-10 10:33:35] magnus@php.net Leave as feedback until you can provide the information we requested.. ------------------------------------------------------------------------ [2003-03-10 09:44:16] hans dot wolters at chello dot nl I need a few hours to setup another machine. Might be tomorrow. Regards, Hans ------------------------------------------------------------------------ [2003-03-10 09:37:16] sniper@php.net andrew: We don't suspend when asking for feedback.. hans: Can you try the latest CVS snapshot? ------------------------------------------------------------------------ [2003-03-10 06:34:54] andrew@php.net Unable to reproduce on WinXP with PHP5 (latest snap), mysql (latest build)... Suspending issue until more feedback is issued. ~ Andrew Heebner ------------------------------------------------------------------------ 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/21890 -- Edit this bug report at http://bugs.php.net/?id=21890&edit=1

« previous php.bugs (#35304) next »