config/debug/gdb.in.gdbserver
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Tue May 08 18:31:10 2012 +0200 (2012-05-08)
changeset 2964 d48c03998dc1
parent 1849 73f76483a389
child 2986 c301df1af7cb
permissions -rw-r--r--
scripts: fix catching failures

POSIX 1003.1-2008 does not say whether "set -e" should catch a sub-shell
that exits with !0 (it has a list of conditions to catch, but no list of
conditions not to catch, and this situation is not listed).

bash-3 does not catch such a failure, but bash-4 does. That why, on my
Squeeze system I did not see the issue, while Thomas did on is Lenny chroot.

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