GNOME Bugzilla – Bug 685250
make <test>.gdb deadlocks
Last modified: 2012-10-21 11:26:21 UTC
We've got check.mk to support running any test as: make -C tests/<dir> <test name>.gdb It's supposed to set all sorts of environment pieces that are a pain to do by hand, run gdb through libtool, etc., so you can just run the test through as if it were a normally-installed program. I just tried this with git master the other day, and it just deadlocks. I have to kill gdb to get the terminal back (and ^C at the terminal does nothing). It looks like it might be related to our lcov support redirecting output (and maybe input?), because I do get a flash of the gdb output when I kill the gdb process.
(In reply to comment #0) > It looks like it might be related to our lcov support redirecting output (and > maybe input?), because I do get a flash of the gdb output when I kill the gdb > process. Probably more likely tests/tools/execute-test.sh.
In fact it’s almost certainly because the output from gdb is being redirected by execute-test.sh, and so you’re never seeing the gdb prompt, and thus never typing the ‘run’ command in gdb.
commit 4b7db8692d58d8627805f4c45a1c2e885b46653c Author: Philip Withnall <philip@tecnocode.co.uk> Date: Sun Oct 21 12:24:10 2012 +0100 Bug 685250 — make <test>.gdb deadlocks Always set CHECK_VERBOSE when running tests under gdb so that output (from gdb) isn’t redirected to a log file. Apparently, headless gdb is hard to use. Closes: https://bugzilla.gnome.org/show_bug.cgi?id=685250 NEWS | 1 + check.mk | 1 + tests/tools/execute-test.sh | 4 +++- 3 files changed, 5 insertions(+), 1 deletion(-)