From: Alvaro Herrera <alvherre@alvh.no-ip.org>
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 12:14:17 -0300
Message-ID: <20071211151416.GD10710@alvh.no-ip.org> (raw)
In-Reply-To: <475EA754.1090307@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>
<20071211112128.GB4708@alvh.no-ip.org>
<475EA754.1090307@emolecules.com>
Craig James wrote:
> Here is my guess -- and this is just a guess. My functions use a
> third-party library which, of necessity, uses malloc/free in the
> ordinary way. I suspect that there's a bug in the Postgres palloc()
> code that's walking over memory that regular malloc() allocates. The
> third-party library (OpenBabel) has been tested pretty thoroughly by
> me an others and has no memory corruption problems. All malloc's are
> freed properly. Does that seem like a possibility?
Not really. palloc uses malloc underneath.
--
Alvaro Herrera Valdivia, Chile ICBM: S 39º 49' 18.1", W 73º 13' 56.4"
"La vida es para el que se aventura"
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: alvherre@alvh.no-ip.org, craig_james@emolecules.com
Subject: Re: libgcc double-free, backend won't die
In-Reply-To: <20071211151416.GD10710@alvh.no-ip.org>
* 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