[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can we go GTK-only?
From: |
Perry E. Metzger |
Subject: |
Re: Can we go GTK-only? |
Date: |
Wed, 2 Nov 2016 23:29:34 -0400 |
On Wed, 02 Nov 2016 22:13:13 +0200 Eli Zaretskii <address@hidden> wrote:
> > From: Stefan Monnier <address@hidden>
> > Cc: address@hidden, address@hidden,
> > address@hidden, address@hidden Date: Wed, 02 Nov 2016
> > 12:04:48 -0400
> > > "Should", not "will". And on some systems, only with very
> > > recent library versions.
> >
> > Again: which system are you think of that's had a buggy
> > malloc-with-threads in the last, say, ten years?
>
> Even glibc had a bug. And one or 2 of *BSDs.
>
Which BSD? Name. Date. And yes, glibc had a bug in free. It caused a
memory leak, not a crash, and it was fixed.
--
Perry E. Metzger address@hidden
- Re: Can we go GTK-only?, (continued)
- Re: Can we go GTK-only?, Stefan Monnier, 2016/11/01
- Re: Can we go GTK-only?, Eli Zaretskii, 2016/11/02
- Re: Can we go GTK-only?, Stefan Monnier, 2016/11/02
- Re: Can we go GTK-only?, Nikolaus Rath, 2016/11/02
- Re: Can we go GTK-only?, Paul Eggert, 2016/11/02
- Re: Can we go GTK-only?, Richard Stallman, 2016/11/02
- Re: Can we go GTK-only?, Nikolaus Rath, 2016/11/02
- Re: Can we go GTK-only?, Eli Zaretskii, 2016/11/02
- Re: Can we go GTK-only?,
Perry E. Metzger <=
- Re: Can we go GTK-only?, John Wiegley, 2016/11/03
- Re: Can we go GTK-only?, John Wiegley, 2016/11/03