| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | fred(at)netarx(dot)com |
| Cc: | "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #1092: Memory Fault in PQsetdbLogin |
| Date: | 2004-03-04 15:45:04 |
| Message-ID: | 26094.1078415104@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> writes:
> When opening two connections using PQsetdbLogin one of the connections was
> apparently being dropped, and I would get segmentation errors.
> I rebuilt the program using dmalloc and it reported...
> debug-malloc library: dumping program, fatal error
> Error: invalid allocation size (err 40)
> ...when PQsetdbLogin was called.
> I replaced the call to PQsetdbLogin with an equivalent call to PQconnectdb.
> dmalloc does not report any errors with PQconnectdb and the original two
> problems seem to have gone away.
This is a bit hard to believe, seeing that as of 7.4 these two functions
are trivial wrappers around the same set of underlying functions.
You're going to need to provide more detail, or preferably a
reproducible test case.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PostgreSQL Bugs List | 2004-03-04 16:33:40 | BUG #1093: wrong handling of additional parameters in init script |
| Previous Message | PostgreSQL Bugs List | 2004-03-04 15:20:43 | BUG #1092: Memory Fault in PQsetdbLogin |