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 | 6C8E163ED7EF5846B2F44CDBC63300110B3EAB1F@SGSIMBX002.nsn-intra.net обсуждение исходный текст |
Ответ на | Re: Not sure if this crash is in psql odbc driver? (Heikki Linnakangas <hlinnakangas@vmware.com>) |
Список | pgsql-odbc |
> 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? We tried to create a self contained program to reproduce the issue but the issue is not observed with self contained program. It is only observed with actual application code. So is why I am not fully confident of issue being in psql odbc driver code but at the same time we do not find any suspicion in using any of the ODBC APIs. We will run the test again with debug enabled psql odbc driver code and share the backtrace. It is multi-threaded application. ODBC configuration is almost all default: # cat odbc.ini [PostgreSQL] Description = data source for PostgreSQL Driver = PostgreSQL # cat odbcinst.ini [PostgreSQL] Description = psql_odbc for PostgreSQL Driver = /opt/PostgresClient/lib/psqlodbcw.so Setup = FileUsage = 1 Threading = 0 -- 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 по дате отправления: