#27828 [Com]: sybase_free_result() crashes

ID: 27828 Comment by: michail dot bachmann at cms dot hu-berlin dot de Reported By: deanb at gbtn dot net Status: Verified Bug Type: Sybase-ct (ctlib) related Operating System: * PHP Version: 4CVS, 5CVS (2004-04-02) New Comment: Hello again, A workaround for this bug is to comment out the line 1602 in php_sybase_ct.c. This function must be broken for a while, since around line 1365 someone fixed the problem the same way. Oh, BTW PHP crashes while freeing result->tmp_buffer in line 1013. Looks like something corrupts the memory around this variable. HTH Previous Comments: ------------------------------------------------------------------------ [2004-04-30 10:38:28] michail dot bachmann at cms dot hu-berlin dot de Hello, this bug still exists in 4.3.6. Calling sybase_free_result crashed Apache (Solaris 8, Apache 1.3.29, Sybase 12.0) Does anyone has a workaround/patch available? ------------------------------------------------------------------------ [2004-04-13 09:41:41] r dot vanicek at seznam dot cz It worked fine in PHP 4.3.4 and PHP 4.3.5RC2, but PHP 4.3.5 (final) is broken, and PHP 4.3.6RC3 is broken too. When sybase_free_result is called, there is segmentation fault (my system is Debian GNU/Linux woody, Apache 1.3.26). ------------------------------------------------------------------------ [2004-04-07 10:46:37] hager at transgene dot fr Hello, same bug with PHP5.0.0-RC1 and the latest PHP5 snapshot PHP5-200404071230 : sybase_free_result() crashes. Should I open a new bug report for PHP 5 ? ------------------------------------------------------------------------ [2004-04-02 13:20:29] deanb at gbtn dot net Nope, same crash with php4-STABLE-200404021630. ------------------------------------------------------------------------ [2004-04-02 06:12:19] derick@php.net 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 ------------------------------------------------------------------------ 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/27828 -- Edit this bug report at http://bugs.php.net/?id=27828&edit=1