#20203 [Fbk->Opn]: odbc_do() or odbc_exec() Always produces a segmentation fault core dump

ID: 20203 User updated by: xmixail@ipnet.gr Reported By: xmixail@ipnet.gr -Status: Feedback +Status: Open Bug Type: ODBC related Operating System: sparc solaris 2.8 and 2.6 PHP Version: 4.2.3 New Comment: Hello again I have already submitted a bug on openlinksw But dont you think that this is a bug of php ? And by the way what is the difference between the 2 functions ? Regards Christos Previous Comments: ------------------------------------------------------------------------ [2002-11-18 10:34:08] kalowsky@php.net Can you please submit a bug with Openlink SW the makers of iODBC. This should work, for all platforms. Please submit a bug at http://www.openlinksw.com/support/online.htm ------------------------------------------------------------------------ [2002-11-18 08:57:51] xmixail@ipnet.gr Hello from Athens AGAIN WOWOWOWOWOW I am happy I removed the line you said from ext/odbc/php_odbc.h and DAMN it works !!!!!!!!!!!!! Thanks very much for your help I anyway think that the bug still exists as fat as SQLExtendedFetch is conserned and has to be resolved in future releases of php (I used 4.2.3) Best regards Christos ------------------------------------------------------------------------ [2002-11-18 08:39:51] xmixail@ipnet.gr Hello again You mean the file ext/odbc/php_odbc.h ?? By the way the openlink "odbctest" program works with SQLFetch and not with SQLExtendedFetch Best Regards Christos ------------------------------------------------------------------------ [2002-11-18 07:13:23] kalowsky@php.net What you're asking is an evil thing, but here goes: In the php_odbc_includes.h file remove the line HAVE_EXTENDED_FETCH from the HAVE_IODBC section of code. Problem is iODBC does work with SQLExtendedFetch. ------------------------------------------------------------------------ [2002-11-18 07:11:37] kalowsky@php.net As with everything OpenSource, gcc. :) ------------------------------------------------------------------------ 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/20203 -- Edit this bug report at http://bugs.php.net/?id=20203&edit=1