From: Tom Lane <tgl@sss.pgh.pa.us>
To: "frank ernest" <doark@mail.com>
cc: pgsql-interfaces@postgresql.org
Subject: Re: segfault in libpq
In-reply-to: 
 <trinity-31011ab9-a78d-449a-b500-6b1d8ccfbc5b-1410797385159@3capp-mailcom-lxa04>
References: 
 <trinity-31011ab9-a78d-449a-b500-6b1d8ccfbc5b-1410797385159@3capp-mailcom-lxa04>
Comments: In-reply-to "frank ernest" <doark@mail.com>
 message dated "Mon, 15 Sep 2014 18:09:45 +0200"
Date: Mon, 15 Sep 2014 09:50:30 -0700
Message-ID: <1086.1410799830@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-interfaces-owner@postgresql.org

"frank ernest" <doark@mail.com> writes:
> Hi, before I report this as a bug I'd like to know if it's my code or not. I'm not going to send the whole function that starts the process since it's several KiB in size (but yell if yu want it anyways.) The problem in libpq is with the vaiable:
> paramValues

It seems very likely that your code is not setting up the paramValues
array the way libpq expects.  Since you've not shown us the code that
prepares that array, nor even the variable declarations, that's just
an educated guess ... but PQexecPrepared has been around for a long
time and there are no other reports of bugs here.

			regards, tom lane


-- 
Sent via pgsql-interfaces mailing list (pgsql-interfaces@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-interfaces