[Buildroot] [PATCH] toolchain: introduce config options to include GCC's sanitation libraries

Markus Mayer mmayer at broadcom.com
Sat Oct 26 21:49:04 UTC 2019


On Sat, 26 Oct 2019 at 12:03, Matthew Weber <matthew.weber at collins.com> wrote:
>
> Markus,
>
> On Sat, Oct 26, 2019 at 1:29 PM Markus Mayer <mmayer at broadcom.com> wrote:
> >
> > Hi all,
> >
> > On Wed, 5 Jun 2019 at 14:42, Markus Mayer <mmayer at broadcom.com> wrote:
> > >
> > > We add config options for external toolchains to allow copying the
> > > following libraries into the root file system:
> > >
> > >   - libasan (-fsanitize=address)
> > >   - liblsan (-fsanitize=leak)
> > >   - libtsan (-fsanitize=thread)
> > >   - libubsan (-fsanitize=undefined)
> > >
> > > Copying these shared libraries into the root file system will add
> > > run-time support for binaries compiled with one of the above "sanitize"
> > > options for enhanced run-time debugging.
> >
>
> Aside from build time impacts, would there be any reason to not just
> enable these by default in GCC > 4.8 ?

Size considerations would also be a reason not to enable it by
default. I believe BR tries to keep things minimal, and these are
debugging libraries that are not strictly necessary on a production
system.

But I am open to doing it either way. I'll leave it up to the BR
maintainers to make the call one way or another. Regardless of what
the default is, though, it'll be easy to change the settings in a
defconfig file or config fragment.

Regards,
-Markus



More information about the buildroot mailing list