[Bug 665188] Re: QVariant and ODBC for iSeries segmentation fault in text field.

2012-02-04 Thread Mondin Marco
I made a mistake, the working code is as follows: if(unicode) { QVarLengthArraySQLTCHAR buftmp(colSize); memset(buftmp.data(), 0, colSize*sizeof(SQLTCHAR)); r = SQLGetData(hStmt, column+1, SQL_C_TCHAR, (SQLPOINTER)buftmp.data(), 0, lengthIndicator); -- You received this bug notification because

[Bug 665188] Re: QVariant and ODBC for iSeries segmentation fault in text field.

2012-02-03 Thread Mondin Marco
I found the source of the problem and a solution. In qsql_odbc.cpp file (at line 373 of QT4 version 4.7.4) is the following: if(unicode) { r = SQLGetData(hStmt, column+1, SQL_C_TCHAR, NULL, 0, lengthIndicator); The problem is in the NULL pointer. If the lines are corrected as follows, the

[Bug 665188] Re: QVariant and ODBC for iSeries segmentation fault in text field.

2012-01-17 Thread Mondin Marco
questo bug affligge ubuntu e fedora sia a 32bit che a 64 bit a partire dalle This bug affects ubuntu and fedora both 32bit and 64bit versions from where unixODBC has taken the place of iODBC. Although the newer versions have libiodbc2, you can not use it because soar QT4 has been compiled with

[Bug 665188] Re: QVariant and ODBC for iSeries segmentation fault in text field.

2011-01-11 Thread Mondin Marco
Here is gdb output: ma...@marco-desktop:~/src/g-suite/gfat$ gdb gfat GNU gdb (GDB) 7.2-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is

[Bug 665188] Re: QVariant and ODBC for iSeries segmentation fault in text field.

2011-01-11 Thread Mondin Marco
Here is gdb bt output: (gdb) bt #0 0x75d0cba5 in raise (sig=value optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x75d106b0 in abort () at abort.c:92 #2 0x75d05a71 in __assert_fail ( assertion=0x75e22c40 outbuf != ((void *)0) *outbuf != ((void

[Bug 665188] Re: QVariant and ODBC for iSeries segmentation fault in text field.

2010-10-26 Thread Mondin Marco
Following is the gdb bugtrace: #0 0x75d0cba5 in raise () from /lib/libc.so.6 #1 0x75d106b0 in abort () from /lib/libc.so.6 #2 0x75d05a71 in __assert_fail () from /lib/libc.so.6 #3 0x75cf93a3 in ?? () from /lib/libc.so.6 #4 0x75cf882c in iconv () from

[Bug 665188] Re: QVariant and ODBC for iSeries segmentation fault in text field.

2010-10-25 Thread Mondin Marco
** Description changed: Binary package hint: libqt4-sql-odbc - Ubuntu / Kubuntu 4.10 everything worked perfectly. + Ubuntu / Kubuntu 10.04 everything worked perfectly. With ubuntu / kubuntu 10.10, accessing a database on the IBM iSeries, using a SELECT query from QT4 application,

[Bug 253952] Re: SELECT don't work in libqt4-sql-odbc with IBM ISeries driver

2010-10-22 Thread Mondin Marco
The problem was fixed in UBUNTU 9.04. Tanks! -- SELECT don't work in libqt4-sql-odbc with IBM ISeries driver https://bugs.launchpad.net/bugs/253952 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing

[Bug 253952] Re: SELECT don't work in libqt4-sql-odbc with IBM ISeries driver

2010-10-22 Thread Mondin Marco
Ehm! 10.04 non 9.04... Excuse me! -- SELECT don't work in libqt4-sql-odbc with IBM ISeries driver https://bugs.launchpad.net/bugs/253952 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list

[Bug 253952]

2010-10-22 Thread Mondin Marco
affects ubuntu/libqt4-sql-odbc status fixreleased -- SELECT don't work in libqt4-sql-odbc with IBM ISeries driver https://bugs.launchpad.net/bugs/253952 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs

[Bug 665188] [NEW] QVariant and ODBC for iSeries segmentation fault in text field.

2010-10-22 Thread Mondin Marco
Public bug reported: Binary package hint: libqt4-sql-odbc Ubuntu / Kubuntu 4.10 everything worked perfectly. With ubuntu / kubuntu 10.10, accessing a database on the IBM iSeries, using a SELECT query from QT4 application, everything works correctly only with numeric fields on the database. If

[Bug 253952] Re: SELECT don't work in libqt4-sql-odbc with IBM ISeries driver

2010-10-22 Thread Mondin Marco
** Changed in: qt4-x11 (Ubuntu) Status: New = Fix Released -- SELECT don't work in libqt4-sql-odbc with IBM ISeries driver https://bugs.launchpad.net/bugs/253952 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 253952] [NEW] SELECT don't work in libqt4-sql-odbc with IBM ISeries driver

2008-08-01 Thread Mondin Marco
Public bug reported: Binary package hint: libqt4-sql-odbc I tested whit ISeriesAccess ODBC driver for linux 1.4 and 1.6 both 32bit. Whit QT4.2 compiled myself worked, but they used unixODBC and not iODBC. qDebug show regulary connection to database, but when I tray to do a SELECT, the result of

[Bug 93413] Re: vpnc dead peer detection disconnects immediately

2008-08-01 Thread Mondin Marco
Excuse me, i lost same thing: A similar aproach, I used that work whit kvpnc is: sudo mv /usr/sbin/vpnc /usr/sbin/vpnc2 sudo nano /usr/sbin/vpnc Put this lines in file: #!/bin/bash /usr/sbin/vpnc2 --dpd-idle 0 $* sudo chmod +x /usr/sbin/vpnc It is a similar solution, but don't hang kvpnc.

[Bug 93413] Re: vpnc dead peer detection disconnects immediately

2008-08-01 Thread Mondin Marco
A similar aproach, I used that work whit kvpnc is: sudo mv /usr/sbin/vpnc /usr/sbin/vpnc2 sudo nano /usr/sbin/vpnc Put this lines in file: #!/bin/bash --dpd-idle 0 $* sudo chmod +x /usr/sbin/vpnc It is a similar solution, but don't hang kvpnc. -- vpnc dead peer detection disconnects

[Bug 179261] Re: libqt4-sql does not include QODBC

2008-07-30 Thread Mondin Marco
I trayed the 4.4.0-1ubuntu5~hardy1~ppa2. A little application i made to access my ISeries with ODBC driver, won't work with queries. This application worked in original QT4.2 myself compiled, but not whit this driver. The DB is correctly opened, query.exec() is activated, but query.next() return