Date: Sun, 15 Jan 2006 03:32:49 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Pascal Hofstee <caelian@gmail.com> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, Jason Evans <jasone@FreeBSD.org>, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/stdlib malloc.c Message-ID: <20060115013248.GA28047@flame.pc> In-Reply-To: <43C97BCA.6030201@gmail.com> References: <200601121809.k0CI9QGV028693@repoman.freebsd.org> <AD9B1A12-47F1-4EA1-B270-CC83D3149543@freebsd.org> <20060112182804.GA1047@flame.pc> <20060113012900.GA16082@flame.pc> <554CC8A8-35FB-424A-B883-505C26ECBBE8@FreeBSD.org> <20060114213238.GA15253@flame.pc> <6FD0F2BA-88E3-4E82-A5F8-D89051AEEECA@FreeBSD.org> <43C97BCA.6030201@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-01-14 14:31, Pascal Hofstee <caelian@gmail.com> wrote: > Jason Evans wrote: > >Hmm, that's interesting. I'll mess around with emacs later on today > >(though I only have i386 hardware at the moment). Right now, I'm > >still building xorg on my machine in order to try to reproduce the gtk > >problems that Pascal Hofstee reported. > > Hi Jason .. In the mean while i decided to do a pkg_delete -a followed > by a fresh gnome install from standard ports instead of Joe Marcus > Clarke's MC-gnome tree .. and it looks like the main culprit is > glib-2.9.2 as the observed GTK-problems do not occur with the glib20 > port that is currently in the main ports-tree. So i think it's safe to > assume glib-2.9.2 is seriously busted and jemalloc just happened to > Really get pissed about it :) Hmmm, this is very interesting. I see that irssi links to glib-2.8.5 here, but where did you get a port for glib of a newer version?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060115013248.GA28047>