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

From: Andrew Klosterman <andrew5(at)ece(dot)cmu(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2246: Bad malloc interactions: ecpg, openssl
Date: 2006-02-14 21:02:17
Message-ID: Pine.LNX.4.53L-ECE.CMU.EDU.0602141601120.29413@blossom.pdl.cmu.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

> We may be spending too much time on this one point --- as long as
> Kerberos isn't *writing* into the zero-length alloc, there is nothing
> illegal immoral or fattening about malloc(0). Can you get ElectricFence
> to not abort right here but continue on to the real problem?
>
> regards, tom lane

Doing a "man efence" lets me know that setting the EF_ALLOW_MALLOC_0
environment variable ought to let the program continue... I'll check into
that right now!

--Andrew J. Klosterman
andrew5(at)ece(dot)cmu(dot)edu

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephen Frost 2006-02-14 21:10:33 Re: BUG #2246: Bad malloc interactions: ecpg, openssl
Previous Message Tom Lane 2006-02-14 20:51:43 Re: BUG #2246: Bad malloc interactions: ecpg, openssl

Browse pgsql-patches by date

  From Date Subject
Next Message Kris Jurka 2006-02-14 21:10:30 Re: add additional options to CREATE TABLE ... AS
Previous Message Martijn van Oosterhout 2006-02-14 21:00:50 Re: Patch Submission Guidelines