2012-10-21scripts/functions: return a proper error code in CT_DoExecLog
"Yann E. MORIN" <yann.morin.1998@free.fr> [Sun, 21 Oct 2012 22:27:17 +0200] rev 3085
scripts/functions: return a proper error code in CT_DoExecLog

Since we added the debug-shell feature, CT_DoExecLog no longer
returns the error code of the command, but always return 0.

This breaks the download mechanism, which relies on CT_DoExecLog
to fail _on_purpose_ to detect that the ressource was not found
at the specified URL.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

2012-10-17scripts/functions: properly catch failure in CT_Test* helpers
"Yann E. MORIN" <yann.morin.1998@free.fr> [Wed, 17 Oct 2012 22:01:25 +0200] rev 3084
scripts/functions: properly catch failure in CT_Test* helpers

So we get caught by the trap-handler and
have a chance to run the debug-shell.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Johannes Stezenbach <js@sig21.net>

2012-10-06scripts: add option to start an interactive debug shell
"Yann E. MORIN" <yann.morin.1998@free.fr> [Sat, 06 Oct 2012 23:48:07 +0200] rev 3083
scripts: add option to start an interactive debug shell

Add an option that, when a command fails:
- starts an interactive shell with the failed command's environment
- attempts re-execution of the failed command, continues, or aborts
at user's whim.

Before starting the debug-shell, the backtrace is printed.
When exiting for an abort, the standard error message is printed.

Based on an idea and a patch from: Johannes Stezenbach <js@sig21.net>
http://sourceware.org/ml/crossgcc/2012-09/msg00144.html

Signed-off-by: Johannes Stezenbach <js@sig21.net>
[yann.morin.1998@free.fr: integrate in the fault handler]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Johannes Stezenbach <js@sig21.net>
Patchwork-Id: 191571
Patchwork-Id: 191668