| From: | "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #1092: Memory Fault in PQsetdbLogin |
| Date: | 2004-03-04 15:20:43 |
| Message-ID: | 20040304152043.31521CF4C9D@www.postgresql.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 1092
Logged by: Fred Eisele
Email address: fred(at)netarx(dot)com
PostgreSQL version: 7.4
Operating system: Debian/GNU unstable (kernel 2.6.3)
Description: Memory Fault in PQsetdbLogin
Details:
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.
As far as I am concerned, deprecating PQsetdbLogin is an adequate fix.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-03-04 15:45:04 | Re: BUG #1092: Memory Fault in PQsetdbLogin |
| Previous Message | Tatsuo Ishii | 2004-03-04 03:09:45 | Re: BUG #1091: Localization in EUC_TW Can't decode Big5 |