scripts/build/kernel/bare-metal.sh
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 965 45ddf096def1
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@861
     1
# This file declares functions for bare metal kernel (IE. none)
yann@861
     2
# Copyright 2008 Yann E. MORIN
yann@861
     3
# Licensed under the GPL v2. See COPYING in the root of this package
yann@861
     4
yann@965
     5
CT_DoKernelTupleValues() {
yann@965
     6
    # For bare-metal, there is no kernel part in the tuple
yann@965
     7
    CT_TARGET_KERNEL=
yann@965
     8
}
yann@965
     9
yann@861
    10
do_kernel_get() {
yann@861
    11
    :
yann@861
    12
}
yann@861
    13
yann@861
    14
do_kernel_extract() {
yann@861
    15
    :
yann@861
    16
}
yann@861
    17
yann@861
    18
do_kernel_headers() {
yann@861
    19
    :
yann@861
    20
}