summaryrefslogtreecommitdiff
path: root/config/global/ct-behave.in
diff options
context:
space:
mode:
Diffstat (limited to 'config/global/ct-behave.in')
-rw-r--r--config/global/ct-behave.in19
1 files changed, 19 insertions, 0 deletions
diff --git a/config/global/ct-behave.in b/config/global/ct-behave.in
index bbe4324..6256a34 100644
--- a/config/global/ct-behave.in
+++ b/config/global/ct-behave.in
@@ -87,4 +87,23 @@ config NO_OVERIDE_LC_MESSAGES
Say N, please.
+config DEBUG_INTERACTIVE
+ bool
+ prompt "Interactive shell on failed commands"
+ help
+ If you say 'y' here, then an interactive shell will be spawned for
+ each failed command.
+
+ This shell will have the same environment that the failed command
+ was run with, and the working directory will be set to the directory
+ the failed command was run in.
+
+ After you fix the issue, you can exit the interactive shell with any
+ of these exit codes:
+ 1 the issue was fixed, continue the build with the next command
+ 2 the issue was fixed, re-run the failed command
+ 3 abort the build
+
+ Note: '2' is only possible for commands run via CT_DoExecLog, though.
+
endif