Re: Not sure if this crash is in psql odbc driver?

Hi,

The attached file in previous mail contains full backtrace. Anyway I am printing the frame 0 for quick reference.

738 Thread 1 (LWP 7532):
739 #0 0x000000555aec5d7c in memcpy () from /lib64/libc.so.6
740 No symbol table info available.
742 func = 0x559ba1a808 "copy_and_convert_field"
743 value = 0x559c229c90 ""
744 opts = 0x559c076210
745 gdata = 0x559c0763c8
746 len = 1252
747 copy_len = 1252
748 needbuflen = 0
749 std_time = {infinity = 0, m = 7, d = 16, y = 2014, hh = 0, mm = 0, ss = 0, fr = 0}
750 stmt_t = 1405483185
751 tim = 0x55a7fd6d98
752 tm = {tm_sec = 45, tm_min = 59, tm_hour = 6, tm_mday = 16, tm_mon = 6, tm_year = 114, tm_wday = 3, tm_yday = 196, tm_isdst = 1, tm_gmtoff = 10800, tm_zone = 0x120d04960 "EEST"}
753 pcbValueOffset = 0
754 rgbValueOffset = 0
755 rgbValueBindRow = 0x55a7fd7310 ""
756 pcbValueBindRow = 0x55a7fd7298
757 pIndicatorBindRow = 0x55a7fd7298
758 ptr = 0x0
759 bind_row = 0
760 bind_size = 0
761 result = 0
762 conn = 0x559c072d30
763 changed = 0
764 text_handling = 0
765 localize_needed = 0
766 neut_str = 0x559c229c90 ""
767 midtemp = {"\000\000\000U\234#oP", '\000' <repeats 11 times>, "\001", '\000' <repeats 11 times>, '\000' <repeats 31 times>}
768 mtemp_cnt = 0
769 pgdc = 0x559c0763c8
770 wconverted = 0
771 g = {Data1 = 0, Data2 = 0, Data3 = 0, Data4 = "\000\000\000\000\000\000\002"}

--
Regards,
Prakash I.

-----Original Message-----
From: ext Inoue, Hiroshi [mailto:inoue(at)tpf(dot)co(dot)jp]
Sent: Thursday, July 24, 2014 5:15 AM
To: Itnal, Prakash (NSN - IN/Bangalore)
Cc: ext Heikki Linnakangas; pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] Not sure if this crash is in psql odbc driver?

(2014/07/21 19:43), Itnal, Prakash (NSN - IN/Bangalore) wrote:
> Hi,
>
> Recently we tested this with debug version of psql-odbc driver. Attached is the backtrace. Due security policies I have delete certain sections which are any way not relevant from backtrace.
>
> ODBC version: Latest ODBC code from trunk
> Postgres server version: 9.1
> Unix ODBC: 2.2.14
> Target Architecture: mips-64
> Scenario: Restart (server and client both running on same HW unit)
>
>
> Below is quick summary from backtrace:
>
> From backtrace:
> Thread 1 (LWP 7532):
> #0 0x000000555aec5d7c in memcpy () from /lib64/libc.so.6
> No symbol table info available.
> #1 0x000000559b99dd08 in copy_and_convert_field (stmt=0x559c076130, field_type=17, atttypmod=-1, valuei=0x559c229c90, fCType=-2, precision=0, rgbValue=0x55a7fd7310, cbValueMax=1252, pcbValue=0x55a7fd7298, pIndicator=0x55a7fd7298) at convert.c:1793
> .
> .
> ptr = 0x0

What's the value of len?

regards.
Hiroshi Inoue

> .
> .
>
>
> From code:
> 1788 if (cbValueMax > 0)
> 1789 {
> 1790 copy_len = (len > cbValueMax) ? cbValueMax : len;
> 1791
> 1792 /* Copy the data */
> 1793 memcpy(rgbValueBindRow, ptr, copy_len);
> 1794
> 1795 /* Adjust data_left for next time */
> 1796 if (stmt->current_col >= 0)
> 1797 pgdc->data_left -= copy_len;
> 1798 }
>
> Since the ptr is 0x0 (NULL), the memcpy is failed. We are not able to debug it fully since we are not fully competent with psqlODBC code base.
>
> It would be of great help if someone helps to resolve this!
>
> --
> Regards,
> Prakash I.