From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig James <craig_james@emolecules.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: libgcc double-free, backend won't die
Date: Tue, 11 Dec 2007 10:07:13 -0500
Message-ID: <7891.1197385633@sss.pgh.pa.us> (raw)
In-Reply-To: <475E4133.5080009@emolecules.com>
References: <C34DDC3D.43F60%llonergan@greenplum.com>
<7EB0D6C0-48E2-4155-8559-9113D3BD2785@ketema.net>
<4728CF7B.7040306@gmail.com>
<4728FB3E.3070709@shaw.ca>
<472978BE.9@hagander.net>
<4729B1E9.2080306@gmail.com>
<475E4133.5080009@emolecules.com>
Craig James <craig_james@emolecules.com> writes:
> This is driving me crazy. I have some Postgres C function extensions in a shared library. They've been working fine. I upgraded to Fedora Core 6 and gcc4, and now every time psql(1) disconnects from the server, the serverlog gets this message:
> *** glibc detected *** postgres: mydb mydb [local] idle: double free or corruption! (!prev): 0x08bfcde8
Have you tried attaching to one of these processes with gdb to see where
it ends up? Have you checked to see if the processes are becoming
multi-threaded?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, craig_james@emolecules.com
Subject: Re: libgcc double-free, backend won't die
In-Reply-To: <7891.1197385633@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox