From: | Craig James <craig_james(at)emolecules(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: libgcc double-free, backend won't die |
Date: | 2007-12-11 15:17:17 |
Message-ID: | 475EA9FD.9000706@emolecules.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Alvaro Herrera wrote:
> 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.
But some Postgres code could be walking off the end of a malloc'ed block, even if palloc() is allocating and deallocating correctly. Which is why I was hoping to use valgrind to see what's going on.
Thanks,
Craig
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-12-11 15:20:10 | Re: libgcc double-free, backend won't die |
Previous Message | Alvaro Herrera | 2007-12-11 15:14:17 | Re: libgcc double-free, backend won't die |