patches/strace/4.5.15/110-dont-use-REG_SYSCALL-for-sh.patch
author |
"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> |
|
Tue Dec 13 23:32:39 2011 +0100 (2011-12-13) |
changeset 2807 |
4193d6e6a174 |
parent 746 |
b150d6f590fc
|
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>
yann@257
|
1 |
diff -dur strace-4.5.15.orig/process.c strace-4.5.15/process.c
|
yann@257
|
2 |
--- strace-4.5.15.orig/process.c 2007-01-11 23:08:38.000000000 +0100
|
yann@257
|
3 |
+++ strace-4.5.15/process.c 2007-07-14 19:19:58.000000000 +0200
|
yann@257
|
4 |
@@ -2679,7 +2679,6 @@
|
yann@257
|
5 |
{ 4*REG_GBR, "4*REG_GBR" },
|
yann@257
|
6 |
{ 4*REG_MACH, "4*REG_MACH" },
|
yann@257
|
7 |
{ 4*REG_MACL, "4*REG_MACL" },
|
yann@257
|
8 |
- { 4*REG_SYSCALL, "4*REG_SYSCALL" },
|
yann@257
|
9 |
{ 4*REG_FPUL, "4*REG_FPUL" },
|
yann@257
|
10 |
{ 4*REG_FPREG0, "4*REG_FPREG0" },
|
yann@257
|
11 |
{ 4*(REG_FPREG0+1), "4*REG_FPREG1" },
|