Date: Thu, 12 Feb 2015 09:27:53 -0500 From: Ed Maste <emaste@freebsd.org> To: Alfred Perlstein <alfred@freebsd.org> Cc: Glen Barber <gjb@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, Ian Lepore <ian@freebsd.org> Subject: Re: HEADS-UP: Enabling WITH_DEBUG_FILES by default Message-ID: <CAPyFy2BZ2PWddVRje0boChhbOqd2C37ztSORqf-sNTuPeD5mSA@mail.gmail.com> In-Reply-To: <54DC2F5B.8080709@freebsd.org> References: <20150212023912.GG1302@hub.FreeBSD.org> <CAPyFy2CSDaukZhJeC3t0%2BccuGW=VTJRT4BoXCNrTUYB%2BxpM5AA@mail.gmail.com> <1423713360.80968.89.camel@freebsd.org> <20150212041158.GH1302@hub.FreeBSD.org> <1423714981.80968.100.camel@freebsd.org> <20150212042857.GJ1302@hub.FreeBSD.org> <54DC2F5B.8080709@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11 February 2015 at 23:43, Alfred Perlstein <alfred@freebsd.org> wrote: > > Agreed, SMALL platforms should turn off at decision of those platform > maintainers. Won't fight to keep debug default on for arm, that's for sure. Actually, it's even more important that we build and store debug files for ARM releases. Consider a user running FreeBSD on a Raspberry Pi, using an image they downloaded and dd'd onto an SD card. The advice "rebuild with debug data and try to reproduce the issue" is more absurd there than on a big amd64 machine. All of this concerns what is on the installation media and in the release package sets, though, and not necessarily the default setting of the knob. It is technically possible for the release builds to enable debug files but leave the default off in the tree, although there are disadvantages of doing so.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2BZ2PWddVRje0boChhbOqd2C37ztSORqf-sNTuPeD5mSA>