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

On Tue, Dec 11, 2007 at 07:50:17AM -0800, Craig James wrote:
> Alvaro Herrera wrote:
> >>>...Since you've now shown that OpenBabel is
> >>>multithreaded, then that's a much more likely cause.
> >>Can you elaborate? Are multithreaded libraries not allowed to be
> >>linked to Postgres?
> >
> >Absolutely not.
>
> Ok, thanks, I'll work on recompiling OpenBabel without thread support.
>
> Since I'm not a Postgres developer, perhaps one of the maintainers could
> update the Postgres manual. In chapter 32.9.6, it says,
>
> "To be precise, a shared library needs to be created."
>
> This should be amended to say,
>
> "To be precise, a non-threaded, shared library needs to be created."
>

Just before someone goes ahead and writes it (which is probably a good idea
in general), don't write it just like taht - because it's platform
dependent. On win32, you can certainly stick a threaded library to it -
which is good, because most (if not all) win32 libs are threaded... Now, if
they actually *use* threads explicitly things might break (but most likely
not from that specifically), but you can link with them without the
problem. I'm sure there are other platforms with similar situations.

//Magnus