malloc crash

Takashi Yano takashi.yano@nifty.ne.jp
Tue Oct 26 16:44:21 GMT 2021


On Tue, 26 Oct 2021 18:03:28 +0200
Corinna Vinschen wrote:
> On Oct 26 10:32, Ken Brown wrote:
> > On 10/26/2021 5:24 AM, Corinna Vinschen wrote:
> > > Ken, is there a chance to tweak the fifo code to stop creating
> > > threads from inside fixup, and to defer the thread start to the first
> > > call in the process actually relying on the thread being started?
> > 
> > I can't think of any way to do that.  The thread is listening for various
> > events that cause it to take action, so it has to always be running.  But I
> > can probably tweak the code so that the thread doesn't have to call malloc
> > early on.
> > 
> > It might take a while to get this right, and the bug has existed ever since
> > I overhauled the fifo code.  So I don't think you have to hold up releasing
> > 3.3.0 while I work on this.
> 
> Try the below patch instead, per Takashi's testing and subsequent discussion.

Your patch works fine for me.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>


More information about the Cygwin-developers mailing list