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
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
