config/debug/gdb.in.gdbserver
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Feb 21 23:39:46 2011 +0100 (2011-02-21)
changeset 2312 8b9938edd3d8
parent 1844 4d6a56579d9d
child 2484 d1a8c2ae7946
permissions -rw-r--r--
libc/glibc: add fortify option

By default, recent versions of glibc and eglibc will build some
functions that take format strings (eg. printf, syslog...) with
run-time checks against some format string attacks. This is
called a fortified build.

Unfortunately, this fails somehow while building the instrumented
version of syslog, with some kind of circular dependency...

Disable fortified builds by default, and hide the enabling option
behind EXPERIMENTAL for daring users...

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 # Menu for the native gdbserver
     2 
     3 config GDB_GDBSERVER
     4     bool
     5     prompt "gdbserver"
     6     default n
     7     depends on ! BARE_METAL
     8     help
     9       Build and install a gdbserver for the target, to run on the target.
    10 
    11 if GDB_GDBSERVER
    12 
    13 config GDB_GDBSERVER_STATIC
    14     bool
    15     prompt "Build a static gdbserver"
    16     default y
    17     help
    18       In case you have trouble with dynamic loading of shared libraries,
    19       you will find that a static gdbserver comes in handy.
    20 
    21 endif # GDB_GDBSERVER
    22 
    23 if BARE_METAL
    24 comment "In bare-metal, you'll need to   "
    25 comment "provide your own gdbserver stub."
    26 endif # BARE_METAL