Re: libpq block allocated before my malloc handler inits?

All I am doing at the moment is spawning a pool of threads each with
their own database connection.  I am using PQconnectdb to create the
database connection when the offending block is deallocated  (this is
largely to answer the other email I got with regards to this).    I just
tried using sslmode=disable in the connection string, to no avail.   It
still crashes with an invalid free.  Perhaps I should try to compile the
database with no SSL in it at all?   Would that make any difference?

Thanks for the input,

Rob Stoddard


Russell Smith wrote:
> rob wrote:
>
>> I am trying to build a small program with libpq as the interface to a
>> Postgre database.  I am using the most current version.  My program
>> uses malloc and free hooks to manage memory without having to request
>> memory from the system all the time.  I expected that the init
>> function (__malloc_initialize_hook)  would run before anything else,
>> but after opening a number of connections to the database with
>> PQconnectdb, my program blows up because of a free which refers to a
>> block of memory that wasn't allocated using my malloc function.  My
>> program runs without a hitch if I comment out the PQconnectdb function
>> calls.
>>
> I've experienced an openSSL, libpq + other library using SSL bug
> recently.  Do you get the same crash is you explicitly disable SSL in
> the connection string?  sslmode=disable.
>
> Thanks
>
> Russell
>