Date: Wed, 27 Jul 2016 17:11:12 -0700 From: Conrad Meyer <cem@freebsd.org> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: freebsd-current <freebsd-current@freebsd.org>, Ed Maste <emaste@freebsd.org> Subject: Re: SafeStack in base Message-ID: <CAG6CVpXxWk1MvAkjygrPaE7pDbiKwvJ12o0U1o_Qyy2GrYC_ug@mail.gmail.com> In-Reply-To: <20160728000530.GH13428@mutt-hardenedbsd> References: <20160727225527.GG13428@mutt-hardenedbsd> <CAG6CVpWgXMNHsdo0doL0FDygykZY3vYm9w8897p4nyetTmGfew@mail.gmail.com> <20160728000530.GH13428@mutt-hardenedbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 27, 2016 at 5:05 PM, Shawn Webb <shawn.webb@hardenedbsd.org> wrote: > On Wed, Jul 27, 2016 at 05:02:07PM -0700, Conrad Meyer wrote: >> The problem appears to be an upstream limitation of >> -fsanitize=safe-stack: "Most programs, static libraries, or individual >> files can be compiled with SafeStack as is. ??? Linking a DSO with >> SafeStack is not currently supported." [0] >> >> That probably needs to be addressed upstream before it can be enabled globally. > > Gotcha. If I'm reading correctly, then, SafeStack can only be enabled in > bsd.prog.mk (and _not_ bsd.lib.mk). Is that correct? That is my reading of the page. I'll admit my total experience with -fsanitize=safe-stack is limited to glancing at the web page 5 minutes ago, so don't consider my take authoritative. Best, Conrad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpXxWk1MvAkjygrPaE7pDbiKwvJ12o0U1o_Qyy2GrYC_ug>