scripts/functions: fix endless loop in debug-shell with IO redirection

CT_DEBUG_INTERACTIVE is disabled when stdin, stdout or
stderr are redirected, but the check is only done at
the start of the build and doesn't catch when individual
build commands use redirection. When stdin is redirected
it will cause the debug shell to exit immediately, causing
and endless loop. Thus, save the stdin/our/err file handles
and restore them before invoking the debug shell.

Signed-off-by: Johannes Stezenbach <js@sig21.net>
Message-Id: <20121030102225.GA8303@sig21.net>
Patchwork-Id: 195409

CT_LOCAL_TARBALLS_DIR="${HOME}/src"

CT_SAVE_TARBALLS=y

CT_LOG_EXTRA=y

CT_ARCH_FLOAT_SW=y

CT_ARCH_powerpc=y

CT_TARGET_VENDOR="unknown_nofpu"

CT_KERNEL_linux=y

CT_KERNEL_V_2_6_31_14=y

CT_BINUTILS_V_2_19_1a=y

CT_BINUTILS_FOR_TARGET=y

CT_CC_V_4_3_2=y

CT_CC_LANG_FORTRAN=y

CT_CC_LANG_CXX=y

CT_CC_LANG_JAVA=y

CT_LIBC_glibc=y

CT_LIBC_GLIBC_V_2_9=y

# CT_LIBC_GLIBC_FORCE_UNWIND is not set

CT_LIBC_GLIBC_USE_PORTS=y

CT_DEBUG_dmalloc=y

CT_DEBUG_duma=y

CT_DEBUG_gdb=y

CT_GDB_NATIVE=y

CT_DEBUG_strace=y

CT_GMP_V_4_3_2=y

CT_MPFR_V_2_4_2=y