ID:               20203
 User updated by:  [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
 Status:           Open
 Bug Type:         ODBC related
 Operating System: sparc solaris 2.8 and 2.6
 PHP Version:      4.2.3
 New Comment:

at /usr/pkg/php/php4-200210311500/ext/odbc/php_odbc.c:1274
1274            convert_to_string_ex(pv_query);
(gdb) n
1277            result = (odbc_result *)emalloc(sizeof(odbc_result));
(gdb) display result
1: result = (odbc_result *) 0x1b4a88
(gdb) display result.stmt
2: result.stmt = 0x1b9da8
(gdb) display /s result.stmt
3: x/s result.stmt  0x1b9da8:    "select * from kan_keim"

At this point the query statment is correct
But just before producing the fault is the following :

1305                            if (SQLSetStmtOption(result->stmt,
SQL_CURSOR_TY
PE, SQL_CURSOR_DYNAMIC)
5: /u rc = 16
4: rc = 16
3: x/s result.stmt  0x1c5148:    ""
2: result.stmt = 0x1c5148
1: result = (odbc_result *) 0x1b9dd8
(gdb) s

Program received signal SIGSEGV, Segmentation fault.
0xfeff55dc in SQLExtendedFetch () from
/usr/local/odbc/lib/sql_st_lt.so

I hope this helps you
Best regards 
Christos


Previous Comments:
------------------------------------------------------------------------

[2002-11-01 09:32:49] [EMAIL PROTECTED]

display query
display result->stmt

------------------------------------------------------------------------

[2002-11-01 06:16:39] [EMAIL PROTECTED]

Please i am not too familiar with gdb can you tell me how
I can print query and result->stmt variables in step #10 ?
Bets regards
Christos

------------------------------------------------------------------------

[2002-10-31 19:45:27] [EMAIL PROTECTED]

Also can you please turn on SQL Logging so we can see which steps are
being processed.  From the looks of it the SQLExtendedFetch is catching
an error condition or possibly a need to re-allocate data and refetch
furth of data. 


I find it hard to believe that the odbc_exect (a very basic part of any
DB layer) isn't working with MSSQL.  What are the types of data you're
trying to extract?

------------------------------------------------------------------------

[2002-10-31 19:31:52] [EMAIL PROTECTED]

On step #10 could you print the values of:
query and result->stmt

------------------------------------------------------------------------

[2002-10-31 17:32:40] [EMAIL PROTECTED]

The result is the same after using the latest cvs and here is the
output of gdb 5.0 (and the trace back) :

********************** gdb output *********************
Program received signal SIGSEGV, Segmentation fault.
0xfeff55dc in SQLExtendedFetch () from
/usr/local/odbc/lib/sql_st_lt.so
(gdb) bt
#0  0xfeff55dc in SQLExtendedFetch () from
/usr/local/odbc/lib/sql_st_lt.so
#1  0xfeff6560 in SQLExtendedFetch () from
/usr/local/odbc/lib/sql_st_lt.so
#2  0xfefcc418 in SQLExtendedFetch () from
/usr/local/odbc/lib/sql_st_lt.so
#3  0xfefc76a0 in SQLExtendedFetch () from
/usr/local/odbc/lib/sql_st_lt.so
#4  0xfefc5af0 in SQLExtendedFetch () from
/usr/local/odbc/lib/sql_st_lt.so
#5  0xfefb3584 in SQLNumResultCols () from
/usr/local/odbc/lib/sql_st_lt.so
#6  0xfefac7d0 in SQLError () from /usr/local/odbc/lib/sql_st_lt.so
#7  0xfef97d54 in SQLDriverConnect () from
/usr/local/odbc/lib/sql_st_lt.so
#8  0xfefac89c in SQLExecDirect () from
/usr/local/odbc/lib/sql_st_lt.so
#9  0xff35e72c in SQLExecDirect () from
/usr/local/odbc/lib/libiodbc.so.2
#10 0x4c76c in zif_odbc_exec (ht=1811184, return_value=0x1b4760,
this_ptr=0x0,
    return_value_used=1)
    at /usr/pkg/php/php4-200210311500/ext/odbc/php_odbc.c:1318
#11 0x10a9e0 in execute (op_array=0x1b6110)
    at /usr/pkg/php/php4-200210311500/Zend/zend_execute.c:1595
#12 0xfdb60 in zend_execute_scripts (type=8, retval=0x0, file_count=3)
    at /usr/pkg/php/php4-200210311500/Zend/zend.c:839
#13 0xd699c in php_execute_script (primary_file=0xffbefaf0)
    at /usr/pkg/php/php4-200210311500/main/main.c:1541
#14 0x10ef8c in main (argc=2, argv=0xffbefb7c)
    at /usr/pkg/php/php4-200210311500/sapi/cli/php_cli.c:695

------------------------------------------------------------------------

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

Reply via email to