Date: Tue, 11 Dec 2007 12:14:17 -0300
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
Message-ID: <20071211151416.GD10710@alvh.no-ip.org>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <475EA754.1090307@emolecules.com>
User-Agent: Mutt/1.5.17 (2007-11-01)

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"