1.1 --- a/config/global/ct-behave.in	Tue May 31 16:27:39 2011 +0200
     1.2 +++ b/config/global/ct-behave.in	Sat Oct 06 23:48:07 2012 +0200
     1.3 @@ -87,4 +87,23 @@
     1.4        
     1.5        Say N, please.
     1.6  
     1.7 +config DEBUG_INTERACTIVE
     1.8 +    bool
     1.9 +    prompt "Interactive shell on failed commands"
    1.10 +    help
    1.11 +      If you say 'y' here, then an interactive shell will be spawned for
    1.12 +      each failed command.
    1.13 +      
    1.14 +      This shell will have the same environment that the failed command
    1.15 +      was run with, and the working directory will be set to the directory
    1.16 +      the failed command was run in.
    1.17 +      
    1.18 +      After you fix the issue, you can exit the interactive shell with any
    1.19 +      of these exit codes:
    1.20 +        1  the issue was fixed, continue the build with the next command
    1.21 +        2  the issue was fixed, re-run the failed command
    1.22 +        3  abort the build
    1.23 +      
    1.24 +      Note: '2' is only possible for commands run via CT_DoExecLog, though.
    1.25 +
    1.26  endif