|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #10408 Bad Sybase-CTlib closing
Submitted: 2001-04-19 15:18 UTC Modified: 2001-05-20 14:41 UTC
From: ocomte at guarantycity dot com Assigned:
Status: Closed Package: Sybase-ct (ctlib) related
PHP Version: 4.0.4pl1 OS: Sun Solaris and Linux
Private report: No CVE-ID: None
 [2001-04-19 15:18 UTC] ocomte at guarantycity dot com
if you run this script :
// error handler function
// this function NEVER RETURN (all errors are FATAL) !!
function myErrorHandler($errno,$ErrorMsg)
{	global $connect_id;
  	echo $ErrorMsg,'</body></html>';	// I want to see this one !!!
	exit();  // global exit of php

// set to the user defined error handler
if (!$connect_id)
	echo "An error in sybase_query !!<br>";	// I don't want to see this message
{	$res=sybase_query('select * from toto',$connect_id);
	if (!$res)
		echo "An error in sybase_query !!<br>";	// I don't want to see this message too
		echo 'No error';
and that the table toto doesn't exist you trigger the myErrorHandler and the script terminate as intended. The problem is that Sybase doesn't seem aware of this and the process will live forever even if it doesn't allow Sybase query any more. So if you run this script a few times all the processes will be sleeping and you will no more be able to make a Sybase query. I think there is a problem in the way you handle the Sybase connexion in a error handler with an exit() call.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2001-04-19 16:03 UTC]
Cannot duplicate this locally, can you provide more info?
 [2001-05-20 14:41 UTC]
No feedback.

- James
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Fri Jun 14 22:01:30 2024 UTC