| From: | Reece Hart <reece(at)harts(dot)net> |
|---|---|
| To: | marcelo Cortez <jmdc_marcelo(at)yahoo(dot)com(dot)ar> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: double free corruption? |
| Date: | 2007-12-31 18:29:04 |
| Message-ID: | 1199125744.15701.29.camel@snafu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2007-12-28 at 12:33 -0300, marcelo Cortez wrote:
> i received the follow message from backend ,it's this
> a bug?
...
> *** glibc detected *** postgres: postgres richelet
> 201.235.11.133(2504) SELECT: double free or corruption
> (!prev): 0x0845d7e8 ***
> ======= Backtrace: =========
Does this happen to be on Novell SLES/SLED 10? I saw this bug
sporadically and in several applications 6-9 months ago. I don't think I
ever knew the cause or even what specifically tickled this problem, but
my recollection is that a Novell patch set fixed it.
I remember that I saw a log of these in /var/log/messages (assuming
you're logging locally). Consider looking there to see if you have other
instances of this bug with other applications.
-Reece
--
Reece Hart, http://harts.net/reece/, GPG:0x25EC91A0
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chuck | 2007-12-31 22:39:02 | basic questions: Postgres with yum on CentOS 5.1 |
| Previous Message | blackwater dev | 2007-12-31 15:34:05 | Re: [TLM] Re: batch insert/update |