#46660 [Opn->Fbk]: Calling mssql_next_result causes a coredump
| From: | iliaa@php.net | Date: | Mon, 24 Nov 2008 18:52:58 +0000 |
| Subject: | #46660 [Opn->Fbk]: Calling mssql_next_result causes a coredump | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-131269@lists.php.net to get a copy of this message | ||
ID: 46660
Updated by: iliaa@php.net
Reported By: michael at laccetti dot com
-Status: Open
+Status: Feedback
Bug Type: Reproducible crash
Operating System: Solaris 10 (SPARC)
PHP Version: 5.2.6
New Comment:
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php
for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php
for Win32
Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2008-11-24 16:35:38] michael at laccetti dot com
Description:
------------
After calling a stored procedure that returns multiple resultsets,
trying to call mssql_next_result causes PHP to coredump.
Reproduce code:
---------------
$this->RecordSet = mssql_query($query, $this->DBConn );
if(mssql_next_result($this->RecordSet)) {
error_log("We got more results!");
} else {
error_log("No more results. Waah.");
}
Expected result:
----------------
I expect to see either "We got more results" or "No more results.
Waah." in the logs.
Actual result:
--------------
[Mon Nov 24 11:18:03 2008] [notice] child pid 5515 exit signal Bus
error (10), possible coredump in /usr/local/apache2
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=46660&edit=1