Date: Tue, 17 Jan 2006 07:30:21 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Goran Gajic <ggajic@afrodita.rcub.bg.ac.yu> Cc: freebsd-current@www.freebsd.org Subject: Re: recent changes to libc on amd64 Message-ID: <20060117153021.GA22577@troutmask.apl.washington.edu> In-Reply-To: <Pine.LNX.4.63.0601171543570.7222@afrodita.rcub.bg.ac.yu> References: <Pine.LNX.4.63.0601151319150.30428@afrodita.rcub.bg.ac.yu> <84dead720601170605m406353b5nfbe9e4f2890b59b4@mail.gmail.com> <Pine.LNX.4.63.0601171543570.7222@afrodita.rcub.bg.ac.yu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 17, 2006 at 03:52:58PM +0100, Goran Gajic wrote: > > I have already tried - malloc.c 1.93, 1.94 and 1.95 seems to break > joe and Xorg on amd64 (so far only two applications I have found not > working). On i386 so far I haven't experienced such problems. > I have tried switching back to malloc.c 1.92 and I don't experience any > problems on amd64. Running joe through gdb reports that it breaks > somewhere in libncurses.. The problem with Xorg on amd64 is known, and I believe Jason intends to look into the problem when his hardware arrives. The prolem with joe appears to be new. Can you build libncurses and joe with debugging symbol to get more information? Can rebuild joe with electric fence? Also, read the malloc manpage for setting various flags. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060117153021.GA22577>