Re: Not sure if this crash is in psql odbc driver?
От | Itnal, Prakash (NSN - IN/Bangalore) |
---|---|
Тема | Re: Not sure if this crash is in psql odbc driver? |
Дата | |
Msg-id | 6C8E163ED7EF5846B2F44CDBC63300110B3EB4A4@SGSIMBX002.nsn-intra.net обсуждение исходный текст |
Ответ на | Re: Not sure if this crash is in psql odbc driver? (Heikki Linnakangas <hlinnakangas@vmware.com>) |
Ответы |
Re: Not sure if this crash is in psql odbc driver?
(Heikki Linnakangas <hlinnakangas@vmware.com>)
|
Список | pgsql-odbc |
Please find the backtrace with debug enabled psqlODBC driver. This time we encountered abort. The requested table has onlyone row. Thread 1 (LWP 7326): #0 0x000000556380aff0 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x000000556380f8fc in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x00000055638459e4 in __libc_message () from /lib64/libc.so.6 No symbol table info available. #3 0x0000005563851ec4 in malloc_printerr () from /lib64/libc.so.6 No symbol table info available. #4 0x0000005563856f04 in free () from /lib64/libc.so.6 No symbol table info available. #5 0x0000005581d8d200 in QR_free_memory (self=0x5563951a70) at qresult.c:463 num_backend_rows = 366742936192 num_fields = 0 #6 0x0000005581d8c6f0 in QR_close_result (self=0x5563951a70, destroy=1) at qresult.c:273 conn = 0x120f80cd0 next = 0x5581d8c8a4 top = 1 #7 0x0000005581d8c8c8 in QR_Destructor (self=0x5563951a70) at qresult.c:327 No locals. #8 0x0000005581dafc04 in SC_recycle_statement (self=0x120dbbdc0) at statement.c:886 func = 0x5581dee0b8 "SC_recycle_statement" conn = 0x120f709e0 res = 0x5563951a70 #9 0x0000005581daf924 in SC_initialize_and_recycle (self=0x120dbbdc0) at statement.c:802 No locals. #10 0x0000005581d7b76c in PGAPI_ExecDirect (hstmt=0x120dbbdc0, szSqlStr=0x55930762a8 "SELECT wbts_id FROM act_wbts WHEREwbts_id=130", cbSqlStr=-3, flag=1) at execute.c:161 stmt = 0x120dbbdc0 result = 0 func = 0x5581de5e10 "PGAPI_ExecDirect" conn = 0x120f709e0 #11 0x0000005581dc129c in SQLExecDirect (StatementHandle=0x120dbbdc0, StatementText=0x55930762a8 "SELECT wbts_id FROM act_wbtsWHERE wbts_id=130", TextLength=-3) at odbcapi.c:364 func = 0x5581def670 "SQLExecDirect" ret = 0 stmt = 0x120dbbdc0 flag = 1 #12 0x0000005563d69858 in SQLExecDirect () from /usr/lib64/libodbc.so.2 No symbol table info available. #13 0x00000055631136b4 in db_ExecDirect1 (stmt1=0x5593076250, query=0x55930762a8 "SELECT wbts_id FROM act_wbts WHERE wbts_id=130")at ../src/db_utilityqx.c:923 -- Regards, Prakash I. -----Original Message----- From: ext Heikki Linnakangas [mailto:hlinnakangas@vmware.com] Sent: Monday, June 23, 2014 1:36 PM To: Itnal, Prakash (NSN - IN/Bangalore); pgsql-odbc@postgresql.org Subject: Re: [ODBC] Not sure if this crash is in psql odbc driver? On 06/23/2014 08:50 AM, Itnal, Prakash (NSN - IN/Bangalore) wrote: > Hi, > > We encountered a crash that points to psql odbc driver. The crash is > not at fixed at same point but it always points to psql-odbc driver. It > is at same two places shown below. Kindly let me know if this is really > an issue in psql code! Could be, but it's impossible to track it down without more information. For starters, if you could try with a debug-enabled build of the driver, so that we could see line number information and local variables in the backtrace, that would help. If you can reduce the test to a small self-contained test case that reproduces the crash, that would be best. Can you provide more details on the application and how it uses the driver? Is it multi-threaded? What ODBC functions does it call? What config options are you using? - Heikki
В списке pgsql-odbc по дате отправления:
Предыдущее
От: Craig RingerДата:
Сообщение: Re: msdtc with 32-bit app fails to resolve in-doubt or not-notifed transactions
Следующее
От: Heikki LinnakangasДата:
Сообщение: Git history author/committer fields (was Re: msdtc with 32-bit app fails to resolve in-doubt or not-notifed transactions)