Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
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) 
     1 # ARM specific configuration file

     2 

     3 config ARCH_ARM_MODE

     4     string

     5     default "arm"   if ARCH_ARM_MODE_ARM

     6     default "thumb" if ARCH_ARM_MODE_THUMB

     7 

     8 choice

     9     bool

    10     prompt "Default instruction set mode"

    11     default ARCH_ARM_MODE_ARM

    12 

    13 config ARCH_ARM_MODE_ARM

    14     bool

    15     prompt "arm"

    16     help

    17       Defaults to emitting instructions in the ARM mode.

    18 

    19 config ARCH_ARM_MODE_THUMB

    20     bool

    21     prompt "thumb (EXPERIMENTAL)"

    22     depends on EXPERIMENTAL

    23     help

    24       Defaults to emitting instructions in the THUMB mode.

    25 

    26 endchoice

    27 

    28 config ARCH_ARM_INTERWORKING

    29     bool

    30     prompt "Use Thumb-interworking (READ HELP)"

    31     depends on EXPERIMENTAL

    32     help

    33       Excerpt from the gcc manual:

    34       

    35       > Generate code which supports calling between the ARM and Thumb

    36       > instruction sets. Without this option the two instruction sets

    37       > cannot be reliably used inside one program. The default is

    38       > [not to use interwork], since slightly larger code is generated

    39       > when [interwork] is specified.

    40 

    41 config ARCH_ARM_EABI

    42     bool

    43     prompt "Use EABI"

    44     default y

    45     help

    46       Set up the toolchain so that it generates EABI-compliant binaries.

    47 

    48 config ARCH_ARM_ABI_OK

    49     bool

    50     default y

    51     depends on ! ARCH_ARM_EABI

    52     select ARCH_SUPPORT_ABI
crosstool-ng