From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Scot Loach" <sloach(at)sandvine(dot)com>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: segfault when disconnecting from db with server side prepare |
Date: | 2004-09-20 07:39:10 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4306545@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Scot Loach
> Sent: 19 September 2004 15:29
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: [ODBC] segfault when disconnecting from db with
> server side prepare
>
> I think the proper way to fix this is to simply add a check
> for a null pointer in the SC_set_prepared function, but I
> wanted to ask here first since I don't know if this will have
> any unforseen consequences.
Sounds fine to me - it's not like you would ever intentionally want conn
== null in there.
Can you supply a patch?
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Karol Szkudlarek | 2004-09-20 07:58:33 | SQLDescribeCol before SQLExcecute call problem (fwd) |
Previous Message | Scot Loach | 2004-09-19 14:29:07 | segfault when disconnecting from db with server side prepare |