The "kink" I'm working on right now really has me stumped... no PHP errors, no MySQL errors, it looks like it's hit an infinite loop somewhere. I've choked out all the ADODB functions with breakpoints and eliminated all ADODB functions as the cause. When I load it up, it chokes up completely, doesn't display a thing; CPU use for Apache runs at 100% and FireFox just sits there, until I close XSAS. I tested it without modifications and it runs fine, which it's what's most confusing.
I put breakpoints in each of the fetch functions, immediately preceeding the return. The one that chokes (or chokes first, at least) is fetchArray. I've ruled out all other functions using breakpoints.
This:
function fetchArray($result)
{
$row = $result->GetRowAssoc(2);
$result->MoveNext();
die("Works at " . __FILE__ . ", line " . __LINE__);
return $row;
}
chokes up, eventually giving "Fatal error: Maximum execution time of 90 seconds exceeded in W:\www\xoops2\kernel\object.php on line 188", while this:
function fetchArray($result)
{
$row = $result->GetRowAssoc(2);
$result->MoveNext();
// die("Works at " . __FILE__ . ", line " . __LINE__);
return $row;
}
gives the expected "Works at W:\www\xoops2\class\database\mysqldatabase.php, line 139".
Line 188 of kernel/object.php is:
$this->vars[$key]['value'] =& $value;
Which shouldn't lock up under any circumstance. If I drop the old DB class in in place of the new one, it works fine.
Fixing errors is one thing - fixing miscellaneous "it don't work" with no useful error message is quite another. Any thoughts would be greatly appreciated...
I'm running XSAS 1.1 (the latest stable version) with ADODB 4.61 (again, latest stable version.) The ADODB install works for sure - I've used it on the same PC with WAMP with a different project and it works perfectly, and it's pulled from the same zipfile as the one I'm using with XSAS. Neither ADODB install has been modified, and I'm testing this on a clean XOOPS install with no modification other than the DBAL.
