Date: Tue, 07 Oct 2014 23:57:35 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: Antoine Brodin <antoine@freebsd.org> Cc: freebsd-toolchain@freebsd.org, =?windows-1252?Q?Bernhard_Fr=F6hlich?= <decke@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: 11-CURRENT redports builders miscompiling? Message-ID: <543461CF.9040701@FreeBSD.org> In-Reply-To: <CAALwa8nc=wCBKCkcUQu9LOfBqr5NH8XqKxpTXhUDwGZBeQgEUA@mail.gmail.com> References: <201410071915.s97JFrQo061043@svn.freebsd.org> <54343E60.7050208@FreeBSD.org> <CAALwa8k1EejjEk_HFFXVvLGyg4d69UWZoBhHkvydMf5yLe-FCA@mail.gmail.com> <543443CE.6000900@FreeBSD.org> <CAALwa8nc=wCBKCkcUQu9LOfBqr5NH8XqKxpTXhUDwGZBeQgEUA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 07.10.2014 um 22:17 schrieb Antoine Brodin: > So, the test fail on head, but if you look carefully, 1480342*1024 > = 0x5a5a... which looks like malloc junk. Bingo, thanks for the pointer. > But when I turn off malloc debugging ( ln -s 'abort:false,junk:false' > /etc/malloc.conf ) the tests succeed. > > So it looks like a bug in e2fsprogs. Yup, reproduced with "make post-build MALLOC_OPTIONS=J", and valgrind also has something to complain about, so I'll forward a report upstream. I haven't seen something in the "maint" branch since the release that looks like an obvious fix. This lets 11-CURRENT and redports off the hook for now. I wasn't aware redports-on-11 set MALLOC_OPTIONS=J or equivalent. Cheers, Matthias
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?543461CF.9040701>