Re: BUG #2246: Bad malloc interactions: ecpg, openssl

From: Volkan YAZICI <yazicivo(at)ttnet(dot)net(dot)tr>
To: Andrew Klosterman <andrew5(at)ece(dot)cmu(dot)edu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2246: Bad malloc interactions: ecpg, openssl
Date: 2006-02-14 16:06:54
Message-ID: 20060214160654.GA559@alamut
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-bugs pgsql-patches

On Feb 13 04:01, Andrew Klosterman wrote:
> I threw in a pthread mutex around the code making the database connections
> for each of my threads. The problem is still there ("corrupted
> double-linked list").
> ...
> Program received signal SIGILL, Illegal instruction.
> [Switching to Thread 16384 (LWP 24753)]
> 0x401c3851 in kill () from /lib/
> (gdb) bt
> #0 0x401c3851 in kill () from /lib/
> #1 0x40139dd5 in EF_Abort () from /usr/lib/
> #2 0x40139823 in memalign () from /usr/lib/
> #3 0x401399ad in malloc () from /usr/lib/
> #4 0x40139a10 in calloc () from /usr/lib/
> #5 0x404a182f in krb5_set_default_tgs_ktypes () from /usr/lib/
> #6 0x402c8b3f in ?? () from /usr/lib/
> #7 0x402ded88 in ?? () from /usr/lib/
> #8 0x00000000 in ?? ()

I met with some other thread-safety issues caused by libc used in
Debian repos. For instance, getpwuid_r() is broken in Debian's
current stable libc package and this causes a similar memory leak
in the libpq code.

IMHO, testing code with a newer libc version can be the solution.
Otherwise, for an exact answer - as Tom said - we need libpq symbols
in the backtrace.


In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-02-14 17:22:44 Re: BUG #2257: Can' stop server while autovacuum is running
Previous Message Michal Dvoracek 2006-02-14 15:42:53 BUG #2259: never ending select from selects

Browse pgsql-patches by date

  From Date Subject
Next Message Simon Riggs 2006-02-14 17:20:55 Patch Submission Guidelines
Previous Message Tom Lane 2006-02-14 15:47:30 Re: Free WAL caches on switching segments