config/debug/gdb.in.native
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Sat Oct 06 23:48:07 2012 +0200 (2012-10-06)
changeset 3083 3a7b2eee9dcd
parent 2484 d1a8c2ae7946
permissions -rw-r--r--
scripts: add option to start an interactive debug shell

Add an option that, when a command fails:
- starts an interactive shell with the failed command's environment
- attempts re-execution of the failed command, continues, or aborts
at user's whim.

Before starting the debug-shell, the backtrace is printed.
When exiting for an abort, the standard error message is printed.

Based on an idea and a patch from: Johannes Stezenbach <js@sig21.net>
http://sourceware.org/ml/crossgcc/2012-09/msg00144.html

Signed-off-by: Johannes Stezenbach <js@sig21.net>
[yann.morin.1998@free.fr: integrate in the fault handler]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Johannes Stezenbach <js@sig21.net>
Patchwork-Id: 191571
Patchwork-Id: 191668
yann@1849
     1
# Menu for the native GDB
yann@821
     2
yann@583
     3
config GDB_NATIVE
yann@583
     4
    bool
yann@583
     5
    prompt "Native gdb"
yann@850
     6
    depends on ! BARE_METAL
yann@1844
     7
    depends on ! BACKEND
yann@583
     8
    help
yann@583
     9
      Build and install a native gdb for the target, to run on the target.
yann@583
    10
yann@1849
    11
if GDB_NATIVE
yann@1849
    12
yann@1850
    13
config GDB_NATIVE_STATIC
yann@1850
    14
    bool
yann@1850
    15
    prompt "Build a static native gdb"
yann@1850
    16
    help
yann@1850
    17
      In case you have trouble with dynamic loading of shared libraries,
yann@1850
    18
      you will find that a static gdb comes in handy.
yann@1850
    19
yann@1849
    20
endif # GDB_NATIVE