config/arch/arm.in.2
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Dec 13 23:32:39 2011 +0100 (2011-12-13)
branch1.13
changeset 2847 c0bf2319af08
parent 2111 5f4dbeb370e1
child 2788 b6faa28e76e0
permissions -rw-r--r--
scripts: fix dumping execution backtrace

Dumping the backtrace has been broken since changeset #652e56d6d35a:
scripts: execute each steps in a subshell

We can spawn sub-sub-shells in some cases.

The way the fault handler works is to dump the backtrace, but to avoid
printing it once for every sub-shell (which could get quite confusing),
it simply exits when it detects that it is being run in a sub-shell,
leaving to the top-level shell the work to dump the backtrace.

Because each step is executed in its own sub-shell, the variable arrays
that contain the step name, the source file and line number, are lost
when exiting the per-step sub-shell.

Hence, the backtrace is currently limited to printing only the top-level
main procedure of the shell.

Fix this thus:
- when dumping the bckatraces for the steps & the functions, remember
it was dumped, and only dump it if it was not already dumped
- at the top-level shell, print the hints

Also, rename the top-level step label.

Reported-by: Benoît Thébaudeau <benoit.thebaudeau@advansee.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from 4193d6e6a17430a177fa88c287879c2c35e319f3)
yann@628
     1
# ARM specific configuration file
yann@628
     2
yann@1596
     3
config ARCH_ARM_MODE
yann@1596
     4
    string
yann@1596
     5
    default "arm"   if ARCH_ARM_MODE_ARM
yann@1596
     6
    default "thumb" if ARCH_ARM_MODE_THUMB
yann@1596
     7
yann@1596
     8
choice
yann@1596
     9
    bool
yann@1596
    10
    prompt "Default instruction set mode"
yann@1596
    11
    default ARCH_ARM_MODE_ARM
yann@1596
    12
yann@1596
    13
config ARCH_ARM_MODE_ARM
yann@1596
    14
    bool
yann@1596
    15
    prompt "arm"
yann@1596
    16
    help
yann@1596
    17
      Defaults to emitting instructions in the ARM mode.
yann@1596
    18
yann@1596
    19
config ARCH_ARM_MODE_THUMB
yann@1596
    20
    bool
yann@1596
    21
    prompt "thumb (EXPERIMENTAL)"
yann@1596
    22
    depends on EXPERIMENTAL
yann@1596
    23
    help
yann@1596
    24
      Defaults to emitting instructions in the THUMB mode.
yann@1596
    25
yann@1596
    26
endchoice
yann@1596
    27
yann@1597
    28
config ARCH_ARM_INTERWORKING
yann@1597
    29
    bool
yann@1597
    30
    prompt "Use Thumb-interworking (READ HELP)"
yann@1597
    31
    depends on EXPERIMENTAL
yann@1597
    32
    help
yann@1597
    33
      Excerpt from the gcc manual:
yann@1597
    34
      
yann@1597
    35
      > Generate code which supports calling between the ARM and Thumb
yann@1597
    36
      > instruction sets. Without this option the two instruction sets
yann@1597
    37
      > cannot be reliably used inside one program. The default is
yann@1597
    38
      > [not to use interwork], since slightly larger code is generated
yann@1597
    39
      > when [interwork] is specified.
yann@1597
    40
yann@385
    41
config ARCH_ARM_EABI
yann@385
    42
    bool
yann@823
    43
    prompt "Use EABI"
yann@1582
    44
    default y
yann@385
    45
    help
yann@385
    46
      Set up the toolchain so that it generates EABI-compliant binaries.
yann@503
    47
yann@820
    48
config ARCH_ARM_ABI_OK
yann@820
    49
    bool
yann@820
    50
    default y
yann@820
    51
    depends on ! ARCH_ARM_EABI
yann@820
    52
    select ARCH_SUPPORT_ABI