Date: Fri, 13 Jan 2006 22:44:14 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Kris Kennaway <kris@obsecurity.org> Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, freebsd-current@freebsd.org, Jason Evans <jasone@freebsd.org> Subject: Re: HEADSUP: malloc changeover Message-ID: <20060113204414.GA18348@flame.pc> In-Reply-To: <20060113201829.GA24887@xor.obsecurity.org> References: <1A89617A-5F0E-492E-8C21-10A4F679BCD2@freebsd.org> <14547.1137178334@critter.freebsd.dk> <20060113195319.GA17963@flame.pc> <20060113201829.GA24887@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-01-13 15:18, Kris Kennaway <kris@obsecurity.org> wrote: >> I have built & run at least four versions since January 11, two with >> DEBUG_FLAGS='-g' for both userland and kernel and two without. As >> Jason said, we should probably keep looking for potential problems >> both in the new malloc() and the programs that use it[...] > > There are several ports that have build failures due to application > bugs. I think I emailed some of the maintainers already, but there > are more that are going to be (re-)exposed by some more recent changes > than that patchset I was testing. I know :/ I've spent the relatively limited spare time I had the past 2 days trying to track down a segfault & core dump in the build of a CVS snapshot of Emacs. Strangely enough, building with an older version of malloc and then running the same binary with the new version works fine, so this looks like a bug in the multi-stage build of Emacs instead of a really serious malloc bug. I've posted a request for help on emacs-devel and continue trying to nail this down to something more specific than "it crashes when s->data[nbytes]" is accessed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060113204414.GA18348>