kconfig/check.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 943 1cca90ce0481
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@943
     1
#!/bin/sh
yann@943
     2
# Needed for systems without gettext
yann@943
     3
$* -xc -o /dev/null - > /dev/null 2>&1 << EOF
yann@943
     4
#include <libintl.h>
yann@943
     5
int main()
yann@943
     6
{
yann@943
     7
	gettext("");
yann@943
     8
	return 0;
yann@943
     9
}
yann@943
    10
EOF
yann@943
    11
if [ ! "$?" -eq "0"  ]; then
yann@943
    12
	echo -DKBUILD_NO_NLS;
yann@943
    13
fi
yann@943
    14