ID: 22437 Updated by: [EMAIL PROTECTED] Reported By: olle at compound dot se -Status: Feedback +Status: No Feedback Bug Type: ODBC related Operating System: Redhat7.2/kernel 2.4.9 PHP Version: 4.3.1 Assigned To: kalowsky New Comment:
No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2003-03-04 10:35:24] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip ------------------------------------------------------------------------ [2003-02-26 15:32:16] [EMAIL PROTECTED] Try applying the patch at (againt latest stable CVS): http://bb.prohost.org/odbc43.txt If the problem is the result of sprintf() overflow this should correct it. ------------------------------------------------------------------------ [2003-02-26 09:59:02] [EMAIL PROTECTED] >From php_odbc.c: void odbc_do_connect(INTERNAL_FUNCTION_PARAMETERS, int persistent) ... len = strlen(db) + strlen(uid) + strlen(pwd) + sizeof(ODBC_TYPE) + 5; hashed_details = emalloc(len); hashed_len = sprintf(hashed_details, "%s_%s_%s_%s_%d", ODBC_TYPE, db, uid, pwd, cur_opt); ==> shouldn't len include the length of the string representation of cur_opt? Hope this helps, Marc. ------------------------------------------------------------------------ [2003-02-26 09:48:57] [EMAIL PROTECTED] don't change the status.. ------------------------------------------------------------------------ [2003-02-26 09:44:13] olle at compound dot se I have run the Valgrind test with PHP 4.2.3 instead of 4.3.1. The 4.2.3 test produced none of the "Invalid write" messages that 4.3.1 produced. PHP 4.2.3 was built with an identical config-file as 4.3.1. Unfortunately I believe we upgraded from 4.2.3 to get rid of ODBC-problems... ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/22437 -- Edit this bug report at http://bugs.php.net/?id=22437&edit=1
