summaryrefslogtreecommitdiff
path: root/scripts/build/libc/newlib.sh
diff options
context:
space:
mode:
authorYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2011-12-13 22:32:39 (GMT)
committerYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2011-12-13 22:32:39 (GMT)
commit964f379a4290139cf849ed16938b67d4931a950e (patch)
tree91b02dfa8e6ad1585542f9e1355d156ecda1b8eb /scripts/build/libc/newlib.sh
parent06daaa7cc476665181463d2cf2d8d1d57e6165c3 (diff)
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>
Diffstat (limited to 'scripts/build/libc/newlib.sh')
0 files changed, 0 insertions, 0 deletions