php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #46660 Calling mssql_next_result causes a coredump
Submitted: 2008-11-24 16:35 UTC Modified: 2009-06-02 01:00 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: michael at laccetti dot com Assigned:
Status: No Feedback Package: MSSQL related
PHP Version: 5.2.6 OS: Solaris 10 (SPARC)
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: michael at laccetti dot com
New email:
PHP Version: OS:

 

 [2008-11-24 16:35 UTC] 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

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2008-11-24 18:52 UTC] iliaa@php.net 
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.
 [2008-11-26 23:37 UTC] michael at laccetti dot com 
Well, I have a strange problem - when I turn --enable-debug on, the crash stops crashing - everything works as expected.  If I turn it off, it breaks again.  Without --enable-debug, I cannot create the backtrace.
 [2009-05-25 19:51 UTC] kalle@php.net 
Any chance you could provide some more information, such as: MSSQL version, query trying to execute, tables in a reproduce script that always fails.

Does this happen on other systems than Solaris, etc.
 [2009-06-02 01:00 UTC] php-bugs at lists dot php dot net 
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri Oct 04 11:01:28 2024 UTC