Re: Multi-threaded user app segfaults when using libpq with separate connections - Mailing list pgsql-interfaces

From Tom Lane
Subject Re: Multi-threaded user app segfaults when using libpq with separate connections
Date
Msg-id 13531.1060036862@sss.pgh.pa.us
Whole thread Raw
In response to Re: Multi-threaded user app segfaults when using libpq with separate connections  (Frank van Vugt <ftm.van.vugt@foxi.nl>)
Responses Re: Multi-threaded user app segfaults when using libpq with separate connections
SOLVED: Multi-threaded Qt app segfaults when using libpq with separate connections
List pgsql-interfaces
Frank van Vugt <ftm.van.vugt@foxi.nl> writes:
>> You may care to try your test with CVS tip and see if it works better.

> I've retried this with a cvs-version of this afternoon (local
> time). The build stranded in plpgsql (I seem to need a more recent
> bison), but at that point libpq was already finished. This still
> resulted in more or less the same kind of errors.

Are you sure that each thread is accessing only its own PGconn object?

Other than that, not sure what to suggest.  I get the impression that
something is clobbering memory with abandon.  Do you have any
Purify-like tools to look for memory stomp problems?
        regards, tom lane


pgsql-interfaces by date:

Previous
From: Frank van Vugt
Date:
Subject: Re: Multi-threaded user app segfaults when using libpq with separate connections
Next
From: Frank van Vugt
Date:
Subject: Fwd: Re: Multi-threaded user app segfaults when using libpq with separate connections