Re: [Bashdb-devel] Error report in bashdb install

[Rocky B. <roc...@gm...>]

Looks like debugger doesn't get control when a TERM signal given to the
process.

This is on cygwin, right? When I this, I get a slightly different
difference in line number. But in either case this problem is not serious.
I may in the future have this test skipped altogether on cygwin.

On Sun, Jan 25, 2015 at 9:54 PM, Frank Ye <Fra...@ca...> wrote:

> Got error in both two versions:
> bashdb-4.2-0.8/  bashdb-4.3-0.91/
>
>
> ============================================================================
> Testsuite summary for bashdb 4.3-0.91
>
> ============================================================================
> # TOTAL: 42
> # PASS:  38
> # SKIP:  3
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
>
> ============================================================================
> See test/integration/test-suite.log
> Please report to bas...@li...
>
> ============================================================================
> gmake[4]: *** [test-suite.log] Error 1
> gmake[4]: Leaving directory
> `/home/frye/scripts/bashdb-4.3-0.91/test/integration'
> gmake[3]: *** [check-TESTS] Error 2
> gmake[3]: Leaving directory
> `/home/frye/scripts/bashdb-4.3-0.91/test/integration'
> gmake[2]: *** [check-am] Error 2
> gmake[2]: Leaving directory
> `/home/frye/scripts/bashdb-4.3-0.91/test/integration'
> gmake[1]: *** [check-recursive] Error 1
> gmake[1]: Leaving directory `/home/frye/scripts/bashdb-4.3-0.91/test'
> gmake: *** [check-recursive] Error 1
> [frye_CPEGA-1808] ... > less test/integration/test-suite.log
> ======================================================
>    bashdb 4.3-0.91: test/integration/test-suite.log
> ======================================================
>
> # TOTAL: 42
> # PASS:  38
> # SKIP:  3
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> SKIP: test-file-with-spaces
> ===========================
>
> Skipping test due to autoconf problems
>
> ======================================================
>    bashdb 4.3-0.91: test/integration/test-suite.log
> ======================================================
>
> # TOTAL: 42
> # PASS:  38
> # SKIP:  3
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> SKIP: test-file-with-spaces
> ===========================
>
> Skipping test due to autoconf problems
>
> FAIL: test-sig
> ==============
>
> /home/frye/scripts/bashdb-4.3-0.91/test/integration/check-common.sh: line
> 26:  9594 Killed                  $SH -- ${top_builddir}/bashdb $dbg_opts
> -x "$cmdfile" "$debugged_script" $ARGS
> --- /tmp/sig-filtered.check     2015-01-26 10:53:09.800584240 +0800
> +++ /tmp/sig-filtered.right     2015-01-26 10:53:09.795584240 +0800
> @@ -21,7 +21,7 @@
> +handle TERM bogus
> ** Need to give a command: stop, nostop, stack, nostack, print, noprint
> +eval kill -TERM $$
> -$? is 0
> +Program received signal SIGTERM (15)...
> +### Should not have printed a stack trace above...
> +handle TERM noprint
> +handle TERM stack
> @@ -39,10 +39,15 @@
> SIGTERM      stop   noprint showstack trap -- '_Dbg_sig_handler 15
> "$BASH_COMMAND" "$@"' SIGTERM
> +continue
>  Program received signal SIGTERM (15)...
> -->0 in file `sig.sh' at line 55
> -##1 source("sig.sh") called from file `bashdb' at line 96
> -##2 main() called from file `bashdb' at line 0
> +->0 in file `eval.sh' at line 55
> +##1 _Dbg_do_eval("kill", "-TERM", "$$") called from file `processor.sh'
> at line 293
> +##2 _Dbg_onecmd("eval", "kill -TERM $$") called from file `processor.sh'
> at line 202
> +##3 _Dbg_process_commands() called from file `hook.sh' at line 266
> +##4 _Dbg_hook_enter_debugger("after being stepped") called from file
> `hook.sh' at line 182
> +##5 _Dbg_debug_trap_handler("0", "[[ "$1"x != x ]]") called from file
> `sig.sh' at line 7
> +##6 source("sig.sh") called from file `bashdb' at line 96
> +##7 main() called from file `bashdb' at line 0
> +### Should have printed a stack trace above...
> +where 1
> -->0 in file `sig.sh' at line 55
> +->0 in file `eval.sh' at line 55
>
>
> Frank Ye
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Bashdb-devel mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-devel
>