ID: 20203
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Feedback
Bug Type: ODBC related
Operating System: sparc solaris 2.8 and 2.6
PHP Version: 4.2.3
New Comment:
After having spoken with some of the Openlink engineers, and doing my
own tests, I don't believe this is a bug at all in PHP, but rather on
your side.
I haven't been able to reproduce this on any of the local sun boxes I
have to test with either.
Openlink has suggested building a clean version of the library, and
testing further with that.
Previous Comments:
------------------------------------------------------------------------
[2002-11-12 15:41:04] [EMAIL PROTECTED]
1. The sample script is exactly the same expet run on solaris 8so just
the table name is different NOTHING ELSE.
2. here is the trace of SQL :
php ptest3.php
X-Powered-By: PHP/4.2.3
Content-type: text/html
aaa<br>sa<br>
SQLAllocHandle ( ... )
SQLSetStmtAttr ( ... )
SQLAllocHandle ( ... )
SQLConnect ( ... )
SQLGetInfo ( ... )
SQLGetInfo ( ... )
CONNECTION ID = |Resource id #1|
connected to DSN: test
SQLAllocHandle ( ... )
SQLGetStmtAttr ( ... )
SQLGetStmtAttr ( ... )
SQLGetStmtAttr ( ... )
SQLGetStmtAttr ( ... )
SQLGetInfo ( ... )
SQLSetStmtAttr ( ... )
SQLExecDirect ( ... )
Segmentation Fault(coredump)
3. The version of iODBC is 3.0.6 (the latest)
4. I already tried the SQL_CUR_USE_ODBC option and the
result is exacrly the same
5. odbc_prepare produces exactly the same at
SQLPrepare instead of SQLExecDirect (see last line of SQL trace)
6. The variables are corectrly defined and exported in the environment
But even if they exist in the php source the result is exactly the
same
I tried to compiel all in 64 bites (gcc 3.2) with -m64 But it failed
Any idea if this could help ? and how can i compile php with -m64 ??
I would apreciate if you take a look please
Best regards
Christos
------------------------------------------------------------------------
[2002-11-05 17:45:08] [EMAIL PROTECTED]
1) Your sample script and your backtrace do not agree with each other
on what is happening. If you feed me data for another run, I need to
know how that script is working. I can't debug one, when the problem
is in an entirely different format/layout.
2) You still haven't provided a SQL Log. You can enable this in your
odbc.ini file, please read up on the odbc.ini for more information.
3) Which version of iODBC?
4) Did you try to connect using the SQL_CUR_USE_ODBC option?
5) Have you tried using an odbc_prepare command to see if that works.
The error you're seeing is happening within the iODBC system, to which
I have no access to.
6) Why have you commented out the ODBCINI putenv line? Thats generally
a useful line for anything you're going to do with ODBC.
This is as much debugging as I can do right now. My time is rather
commited to other projects right now.
------------------------------------------------------------------------
[2002-11-05 17:10:47] [EMAIL PROTECTED]
Not any idea ??
Pleas help !!
I have a customer waiting
Please if you have any idea Let me know
Christos
------------------------------------------------------------------------
[2002-11-04 10:54:49] [EMAIL PROTECTED]
I use iODBC but this is the log that is produced every time
i run php.
I have compiled with
--without-mysql --with-iodbc
Christos
------------------------------------------------------------------------
[2002-11-04 10:27:30] [EMAIL PROTECTED]
Are you using FreeTDS or iOBDC? I'm very confused...
------------------------------------------------------------------------
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
