All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 12/12] toolchain: improve mudflap support
Date: Thu, 29 Aug 2013 08:18:43 +0200	[thread overview]
Message-ID: <521EE7C3.3050003@mind.be> (raw)
In-Reply-To: <1377671731-28656-13-git-send-email-thomas.petazzoni@free-electrons.com>

On 08/28/13 08:35, Thomas Petazzoni wrote:
> The mudflap library is only useful if one uses the -fmudflap gcc
> option, to do more checks on pointers/arrays, which is typically not
> the case.
>
> This commit:
>
>   * Adds an option to enable/disable mudflap support at the gcc
>     level. By default, it is disabled, which saves a little bit of
>     build time.
>
>   * Adds a way for the external toolchain backend to tell whether
>     mudflap is supported or not by the external toolchain.
>
>   * Adds a global BR2_TOOLCHAIN_HAS_MUDFLAP hidden option, that
>     indicates whether the toolchain (internal or external) supports
>     mudflap.
>
>   * Adds a global BR2_ENABLE_MUDFLAP in "Build options" that allows the
>     user to build all packages with mudflap support. It depends on
>     BR2_TOOLCHAIN_HAS_MUDFLAP.
>
> WARNING WARNING: this currently doesn't result into a working system,
> even with just Busybox. Busybox init crashes with "/sbin/init: symbol
> lookup error: /lib/libmudflapth.so.0: undefined symbol:
> main". According to
> http://gcc.gnu.org/ml/gcc-help/2008-03/msg00165.html  it is caused by
> -Wl,--gc-sections (which is used by Busybox), but even after removing
> it, it still doesn't work. I don't personaly have much interest in
> mudflap support, so as I couldn't get it to work easily, my suggestion
> would be to drop support for it entirely, unless someone steps up to
> fix this issue.

  I would drop the option to enable -fmudflap globally, but keep the 
option to build mudflap support in the internal toolchain. As you wrote 
in another mail, mudflap is a debugging tool and not really a hardening 
tool like SSP.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-08-29  6:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28  6:35 [Buildroot] [PATCH 00/12] Toolchain updates Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 01/12] package/Makefile.in: fix incorrect comment Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 02/12] eglibc: libstdc++ is not part of the C library Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 03/12] toolchain-internal: skip gcc-intermediate when possible Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 04/12] gcc: fix Fortran support Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 05/12] gcc: fix Objective-C support Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 06/12] gcc: move C++ support option next to Fortran/Objective-C Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 07/12] toolchain: add support for glibc Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 08/12] gcc/gcc-final: use the common HOST_GCC_CONFIGURE_SYMLINK macro Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 09/12] gcc: force symlink creation Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 10/12] toolchain: refactor Stack Smashing Protection support Thomas Petazzoni
2013-08-29  6:11   ` Arnout Vandecappelle
2013-08-29  8:34     ` Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 11/12] toolchain: move elf2flt option inclusion to toolchain-buildroot/Config.in Thomas Petazzoni
2013-08-28  6:35 ` [Buildroot] [PATCH 12/12] toolchain: improve mudflap support Thomas Petazzoni
2013-08-29  6:18   ` Arnout Vandecappelle [this message]
2013-08-29  7:56     ` Thomas Petazzoni
2013-08-29 11:24       ` Gustavo Zacarias

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=521EE7C3.3050003@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.