diff options
author | Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> | 2011-12-13 22:32:39 (GMT) |
---|---|---|
committer | Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> | 2011-12-13 22:32:39 (GMT) |
commit | 4235dbd5b8d290d9c426b17bfc5837c47f94049a (patch) | |
tree | 239c15f3953be026af5f18d2c70a496f56d0bdea /patches/gcc/4.2.0/170-missing-execinfo_h.patch | |
parent | 3ee64c2768bb6c26af3b310f2aab818a24acd712 (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>
(transplanted from 4193d6e6a17430a177fa88c287879c2c35e319f3)
Diffstat (limited to 'patches/gcc/4.2.0/170-missing-execinfo_h.patch')
0 files changed, 0 insertions, 0 deletions