diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2020-11-23 17:26:00 -0500 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2020-11-23 17:26:00 -0500 |
| commit | 15a491af3cdc4d7487e848bd9648a15ac3a2d28f (patch) | |
| tree | ab53cc2b6dace943d74de90510816b776e49f25c /gdb/auto-load.c | |
| parent | 891615f060ff6cf8ea5497fd5f07138a52fe4ede (diff) | |
| download | gdb-15a491af3cdc4d7487e848bd9648a15ac3a2d28f.zip gdb-15a491af3cdc4d7487e848bd9648a15ac3a2d28f.tar.gz gdb-15a491af3cdc4d7487e848bd9648a15ac3a2d28f.tar.bz2 | |
gdb/testsuite: show evaluation errors in gdb_assert
Let's say you put this gdb_assert in a test:
gdb_assert "some invalid tcl code"
You just get:
FAIL: gdb.base/template.exp: some invalid tcl code
That's not very easy to debug, since you don't know what's invalid in
your code.
Change gdb_assert to print the error message when catch's return code is
1 (TCL_ERROR). The "warning" is shown both on stdout and in the log
file. Mark the test as unresolved, because the evaluation error means
we couldn't reach a valid pass/fail conclusion.
gdb/testsuite/ChangeLog:
* lib/gdb.exp (gdb_assert): Show error message on error.
Change-Id: Ie6477859554e909ed8d07fb2769c6f2f55e7cce6
Diffstat (limited to 'gdb/auto-load.c')
0 files changed, 0 insertions, 0 deletions