Re: BUG #2246: Bad malloc interactions: ecpg, openssl - Mailing list pgsql-bugs

From Andrew Klosterman
Subject Re: BUG #2246: Bad malloc interactions: ecpg, openssl
Date
Msg-id Pine.LNX.4.53L-ECE.CMU.EDU.0602141612430.29413@blossom.pdl.cmu.edu
Whole thread Raw
In response to Re: BUG #2246: Bad malloc interactions: ecpg, openssl  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, 14 Feb 2006, Andrew Klosterman wrote:

> > 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@ece.cmu.edu

Well, when ElectricFence is allowed to ignore malloc() of zero bytes, my
program runs like a champ!  Might be associated with the replacement
malloc() that it installs to check for bugs, though.

(back to digging some more...)

--Andrew J. Klosterman
andrew5@ece.cmu.edu

pgsql-bugs by date:

Previous
From: Andrew Klosterman
Date:
Subject: Re: BUG #2246: Bad malloc interactions: ecpg, openssl
Next
From: Andrew Klosterman
Date:
Subject: Re: BUG #2246: Bad malloc interactions: ecpg, openssl