| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Indixing problems... |
| Date: | 1998-09-09 14:14:08 |
| Message-ID: | 28308.905350448@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Thomas G. Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> Sadly, that is still true also. As I mentioned earlier, the actual
> segfault happens when memory is free'd toward the end of a query. But of
> course there is some problem earlier when the memory was allocated...
Has anyone tried building the backend with a debugging malloc library?
dbmalloc, or Electric Fence, or Purify would probably help smoke out
any remaining coding errors of this kind (using already-freed space,
writing past the end of a malloc'd block, etc).
Purify is a commercial product, but the other two are freeware and
shouldn't be hard to find on the net.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas G. Lockhart | 1998-09-09 15:10:28 | Re: [HACKERS] Indixing problems... |
| Previous Message | Tom Lane | 1998-09-09 14:05:42 | Re: [HACKERS] new return value of PQfsize |