Bug #4797 Updated: Access Violation cause

From: Date: Sun, 10 Feb 2002 05:00:01 +0000
Subject: Bug #4797 Updated: Access Violation cause
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-36@lists.php.net to get a copy of this message
ID: 4797 Updated by: php-bugs@lists.php.net Reported By: tpowell@villageauction.com -Status: Feedback +Status: No Feedback Bug Type: MSSQL related Operating System: WinNT 4.0 PHP Version: php4-200006081545 New Comment: No feedback was provided for this bug for over a month, 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". Previous Comments: ------------------------------------------------------------------------ [2000-06-13 19:05:05] tpowell@villageauction.com I just tried it an got a "Tried to access invalid memory location" error. Also, on another page with phpinfo() it did not show that the mssql module was loading. When I have more time I'll try poking around a bit more to try to figure out whats going on. But the short answer is that it still isn't working. ------------------------------------------------------------------------ [2000-06-12 23:41:56] zeev@cvs.php.net I just submitted a fix to the CVS. Can you test it? ------------------------------------------------------------------------ [2000-06-12 23:24:50] tpowell@villageauction.com I tried this again on php4-200006081545 and it seems to have the same problem. It still appears that the module isn't peoperly being initialized ------------------------------------------------------------------------ [2000-06-05 19:34:14] fmk@cvs.php.net The fix you applied is not needed. MS_SQL_G(get_column_content)= php_mssql_get_column_content_with_type is called correctly during initialization. ------------------------------------------------------------------------ [2000-06-03 20:41:37] tpowell@villageauction.com I was getting the same error as in report 4540. After poking through the source a bit, I found that it was caused by the mssql_globals structure not being properly initialized. A quick fix was to add the line: MS_SQL_G(get_column_content)= php_mssql_get_column_content_with_type; before the line: MS_SQL_G(get_column_content(mssql_ptr, j, &result->data[i][j-1], column_types[j-1])); in PHP_FUNCTION(mssql_query) However, since this doesn't fix the other parts of the structure that weren't initialized, there are likely other functions where will still be broken. Tim ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=4797&edit=1

« previous php.bugs (#36) next »