Re: libgcc double-free, backend won't die

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"