Re: [PATCH] EXC_BAD_ACCESS in SC_execute - Mailing list pgsql-odbc

From Inoue, Hiroshi
Subject Re: [PATCH] EXC_BAD_ACCESS in SC_execute
Date
Msg-id 53FFC137.9030306@tpf.co.jp
Whole thread Raw
In response to [PATCH] EXC_BAD_ACCESS in SC_execute  (Jade Koskela <jkoskela0@gmail.com>)
List pgsql-odbc
Hi Jade,

(2014/08/27 6:25), Jade Koskela wrote:
> Hello,
>
> I am looking into dmp files which we collect when our application
> crashes. Using google breakpad/stackwalking I am generating the
> stacktrace. The crash looks like this:
>
> Crash reason:  EXC_BAD_ACCESS / 0x0000000d
> Crash address: 0x0
>
> Thread 10 (crashed)
>   0  psqlodbcw.so!SC_Execute    + 0x10bd
>
> I couldn't get the source line so I had to dig through the assembly.
> I was able to determine the error is happening on line statement.c line
> 2191 (from the latest version in the repository).

Did you build binaries from the latest git?

> numcols = QR_NumResultCols(tres);
>     (this expands to)
> numcols = tres->fields->num_fields
>
> The crash happens on the dereference of fields. It could be a null
> pointer, I'm not sure because I can't reproduce the error.
> Apparently EXC_BAD_ACCESS can be SIGSEGV or SIGBUS.
> I have generated a patch to handle the null pointer case.

OK I would check whether fields could be null or not.
It would take some time because I don't have much time.

regards,
Hiroshi Inoue


--
I am using the free version of SPAMfighter.
SPAMfighter has removed 12430 of my spam emails to date.
Get the free SPAMfighter here: http://www.spamfighter.com/len

Do you have a slow PC? Try a Free scan
http://www.spamfighter.com/SLOW-PCfighter?cid=sigen



pgsql-odbc by date:

Previous
From: Jade Koskela
Date:
Subject: debugging symbols
Next
From: Michael Paquier
Date:
Subject: Re: debugging symbols