| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Karl DeBieechop" <kdebisschop(at)alert(dot)infoplease(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #2766: erratic segfault in libpq/DBD::Pg |
| Date: | 2006-11-21 01:33:42 |
| Message-ID: | 16400.1164072822@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Karl DeBieechop" <kdebisschop(at)alert(dot)infoplease(dot)com> writes:
> error is completely erratic - will work 10 times, then fail. or fail 10 time
> then work. So I have not been able to find a reporduacble test case. But
> here's a trace:
> *** glibc detected *** /usr/bin/perl: realloc(): invalid pointer: 0x091c2f94
> ***
This looks like either an extra-free or a memory clobber problem. Try
running your example under a debugging malloc package to see if that
doesn't narrow down the source of the problem. I've had success with
ElectricFence in the past, valgrind might help too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-11-21 01:43:29 | Re: BUG #2769: "invalid memory alloc request size <n>" on startup |
| Previous Message | Bruce Momjian | 2006-11-20 20:33:33 | Re: xlog lockup patch (was: BUG #2712: could not fsync |