Jason Evans wrote:
On Jan 14, 2006, at 1:32 PM, Giorgos Keramidas wrote:
On 2006-01-13 11:07, Jason Evans <[EMAIL PROTECTED]> wrote:
On Jan 12, 2006, at 5:29 PM, Giorgos Keramidas wrote:
Does it look like I'm right in thinking that this is a bug in Emacs?
This looks like a bug in emacs, as you say, but I don't know if it
has any particular relation to the posix_memalign() changes.
Apparently it does seem related to posix_memalign() changes.
When I bootstrap Emacs without posix_memalign(), by manually
tweaking src/config.h after configure runs, and #undef
POSIX_MEMALIGN, then it passes the bootstrap stage normally.
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 :)
I did encounter a malloc bug that's triggered by Evolution resulting in
a runaway process that basically eats up all memory+swap before the
kernel shoots it down .. but i am trying to get gnome@ to help me out on
that one.
But overall i think it's safe to assume that the gtk-issue i reported
earlier is linked to a malloc bug in glib-2.9.2 which is included in the
MC-gnome tree.
--
Pascal Hofstee
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
