mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2025-04-24 04:55:45 +00:00
964f379a42
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>
This is the README for crosstool-NG Crosstool-NG follows the autoconf dance. So, to get you kick-started, just run: ./configure --help You will find the documentation in the directory 'docs'. Here is a quick overview of what you'll find there: 0 - Table of content 1 - Introduction 2 - Installing crosstool-NG 3 - Configuring a toolchain 4 - Building the toolchain 5 - Using the toolchain 6 - Toolchain types 7 - Contributing 8 - Internals A - Credits B - Known issues C - Misc. tutorials You can also point your browser at: http://crosstool-ng.org/ Aloha!