diff options
author | Tom Tromey <tom@tromey.com> | 2016-04-20 10:09:53 -0600 |
---|---|---|
committer | Tom Tromey <tom@tromey.com> | 2016-05-17 12:01:59 -0600 |
commit | dcd1f97951b432032fd0728992b1384064663701 (patch) | |
tree | 8625d7ab7df06b29febb949a96b2a18fe03c475a /gdb/valprint.c | |
parent | e4b8a1c839b88c345b82c37c90814a89c7f0c3c2 (diff) | |
download | gdb-dcd1f97951b432032fd0728992b1384064663701.zip gdb-dcd1f97951b432032fd0728992b1384064663701.tar.gz gdb-dcd1f97951b432032fd0728992b1384064663701.tar.bz2 |
Add self-test framework to gdb
I wanted to unit test the Rust lexer, so I added a simple unit testing
command to gdb.
The intent is that self tests will only be compiled into gdb in
development mode. In release mode they simply won't exist. So, this
exposes $development to C code as GDB_SELF_TEST.
In development mode, test functions are registered with the self test
module. A test function is just a function that does some checks, and
throws an exception on failure.
Then this adds a new "maint selftest" command which invokes the test
functions, and a new dejagnu test case that invokes it.
2016-05-17 Tom Tromey <tom@tromey.com>
* NEWS: Add "maint selftest" entry.
* selftest.h: New file.
* selftest.c: New file.
* maint.c: Include selftest.h.
(maintenance_selftest): New function.
(_initialize_maint_cmds): Add "maint selftest" command.
* configure.ac (GDB_SELF_TEST): Maybe define.
* config.in, configure: Rebuild.
* Makefile.in (SFILES): Add selftest.c.
(COMMON_OBS): Add selftest.o.
2016-05-17 Tom Tromey <tom@tromey.com>
* gdb.texinfo (Maintenance Commands): Document "maint selftest".
2016-05-17 Tom Tromey <tom@tromey.com>
* gdb.gdb/unittest.exp: New file.
Diffstat (limited to 'gdb/valprint.c')
0 files changed, 0 insertions, 0 deletions