Date: Fri, 7 Dec 2018 15:36:32 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: HEADSUP: Something has gone south with -current Message-ID: <20181207233632.GB22981@troutmask.apl.washington.edu> In-Reply-To: <20181207232357.iokl7ay2orkhmdt4@mutt-hbsd> References: <20181207230622.GA22163@troutmask.apl.washington.edu> <20181207232357.iokl7ay2orkhmdt4@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 07, 2018 at 06:23:57PM -0500, Shawn Webb wrote: > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > Dell 7510 laptop was happily running FreeBSD12-alpha9 > > from Oct. 10th. I decided to update to top-of-tree > > today, which would be FreeBSD13 at r341703. > > analysis > > > > make core dumps. > > devd core dumps. > > init core dumps. > > cc core dumps. > > c++ core dumps. > > > > Something seems to be broken. > > There have been (and still are) issues with the introduction of ifunc > in libc (r339898). The symptoms you're describing sound a lot like the > symptoms I experienced early on. > > Do you have any non-standard settings in make.conf/src.conf? > Both are fairly benign. make.conf contains MALLOC_PRODUCTION="YES" and src.conf contains a few WITHOUT_* options (eg, CTM, PPP, NDIS). It seems to be associated with stripping static binaries. See my follow-up post. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181207233632.GB22981>