ID: 35144 User updated by: rberquist at sbdrepro dot com Reported By: rberquist at sbdrepro dot com -Status: Feedback +Status: Open Bug Type: ODBC related Operating System: Highly customized RH PHP Version: 5CVS-2005-11-07 (snap) New Comment:
It crashes with unixODBC but hangs with iodbc. Previous Comments: ------------------------------------------------------------------------ [2005-11-21 18:27:56] [EMAIL PROTECTED] So it doesn't crash, just hangs? ------------------------------------------------------------------------ [2005-11-21 17:16:23] rberquist at sbdrepro dot com Nope, still segfaults. BT is below. I've also attempted to switch to iodbc. I reformatted the odbc.ini files. Using iodbctest, I can connect and query fine. However, after a recompile of php and accessed with php cli, the script executes everything up to the odbc_connect statement. It then stops with no further output as if frozen. No errors are generated or segfaults. If accessed with a browser, the browser simply waits. I have made the phpinfo temporarily available at the following URL. http://ecom.sbdrepro.com/ASP/phpinfo.php (gdb) bt #0 0xb6ec2370 in ?? () #1 0xb6f027b1 in ISAMOpen () from /usr/local/lib/libtfodbccl.so #2 0xb6ef5ace in SQLConnect () from /usr/local/lib/libtfodbccl.so #3 0xb6f5526e in SQLConnect (connection_handle=0x843a468, server_name=0x843047c "CUSTOMER", name_length1=-3, user_name=0x843ea44 "tsi", name_length2=-3, authentication=0x843eabc "", name_length3=-3) at SQLConnect.c:3819 #4 0xb6fa87dc in odbc_sqlconnect (conn=0xbfff7600, db=0x843047c "CUSTOMER", uid=0x843ea44 "tsi", pwd=0x843eabc "", cur_opt=2, persistent=0) at /home/rberquist/php5-200511211530/ext/odbc/php_odbc.c:2174 #5 0xb6fa90c4 in odbc_do_connect (ht=3, return_value=0x843eaf4, return_value_ptr=0x0, this_ptr=0x0, return_value_used=1, persistent=0) at /home/rberquist/php5-200511211530/ext/odbc/php_odbc.c:2373 #6 0xb6fa84d7 in zif_odbc_connect (ht=3, return_value=0x843eaf4, return_value_ptr=0x0, this_ptr=0x0, return_value_used=1) at /home/rberquist/php5-200511211530/ext/odbc/php_odbc.c:2060 #7 0x082751ab in zend_do_fcall_common_helper_SPEC (execute_data=0xbfff7760) at zend_vm_execute.h:188 #8 0x08277e74 in ZEND_DO_FCALL_SPEC_CONST_HANDLER (execute_data=0xbfff7760) at zend_vm_execute.h:1578 #9 0x08274e5b in execute (op_array=0x843a36c) at zend_vm_execute.h:88 #10 0x0824d2c0 in zend_execute_scripts (type=8, retval=0x0, file_count=3) at /home/rberquist/php5-200511211530/Zend/zend.c:1090 ---Type <return> to continue, or q <return> to quit--- #11 0x0820bd51 in php_execute_script (primary_file=0xbfff9b80) at /home/rberquist/php5-200511211530/main/main.c:1704 #12 0x082bb12a in main (argc=2, argv=0xbfff9c64) at /home/rberquist/php5-200511211530/sapi/cli/php_cli.c:1039 ------------------------------------------------------------------------ [2005-11-20 19:40:00] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip ------------------------------------------------------------------------ [2005-11-08 22:01:23] rberquist at sbdrepro dot com Well, using the isql command, the odbc works. With PHP, it does not. This is what has led me to believe that it's not a unixODBC issue. Also, setting up a mysql DSN entry in odbc.ini has proven successful. It connects fine and allows query execution. I've recently found out that it could possibly be the driver and am currently working with the third party developers at the moment. The driver is /usr/local/lib/libtfodbccl.so, which is referenced in the bt. However, they contend that if it works with isql, then the problem is not with the driver. If you have any other ideas for troubleshooting and pinpointing the issue, I'd be happy to comply. ------------------------------------------------------------------------ [2005-11-08 21:44:28] [EMAIL PROTECTED] Are you absolutely sure this isn't a bug in unixODBC? As the backtrace would suggest it's crashing in there, not in PHP. ------------------------------------------------------------------------ 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/35144 -- Edit this bug report at http://bugs.php.net/?id=35144&edit=1
