From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 3/8] Add self-test framework to gdb
Date: Thu, 28 Apr 2016 05:00:00 -0000 [thread overview]
Message-ID: <83inz2xr82.fsf@gnu.org> (raw)
In-Reply-To: <1461789279-15996-4-git-send-email-tom@tromey.com> (message from Tom Tromey on Wed, 27 Apr 2016 14:34:34 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Wed, 27 Apr 2016 14:34:34 -0600
>
> 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
> aborts on failure. I chose this rather than something fancier because
> I think any such failure will require debugging anyhow.
>
> Then this adds a new "maint selftest" command which invokes the test
> functions, and a new dejagnu test case that invokes it.
>
> 2016-04-27 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-04-26 Tom Tromey <tom@tromey.com>
>
> * gdb.texinfo (Maintenance Commands): Document "maint selftest".
>
> 2016-04-26 Tom Tromey <tom@tromey.com>
>
> * gdb.gdb/unittest.exp: New file.
OK for the documentation parts.
Thanks.
next prev parent reply other threads:[~2016-04-28 5:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 20:35 [PATCH v2 0/8] Add Rust language support Tom Tromey
2016-04-27 20:35 ` [PATCH v2 8/8] Rename OP_F90_RANGE to OP_RANGE Tom Tromey
2016-04-27 21:26 ` Pedro Alves
2016-04-27 20:35 ` [PATCH v2 4/8] Add array start and end strings to generic_val_print_decorations Tom Tromey
2016-04-27 20:35 ` [PATCH v2 2/8] Make gdb expression debugging handle OP_F90_RANGE Tom Tromey
2016-04-27 20:35 ` [PATCH v2 7/8] Add Rust documentation Tom Tromey
2016-04-28 4:59 ` Eli Zaretskii
2016-04-27 20:35 ` [PATCH v2 6/8] Update gdb test suite for Rust Tom Tromey
2016-04-27 20:35 ` [PATCH v2 1/8] Fix latent yacc-related bug in gdb/Makefile.in init.c rule Tom Tromey
2016-04-27 20:35 ` [PATCH v2 3/8] Add self-test framework to gdb Tom Tromey
2016-04-28 5:00 ` Eli Zaretskii [this message]
2016-04-28 10:28 ` Yao Qi
2016-04-29 15:13 ` Tom Tromey
2016-04-29 15:29 ` Yao Qi
2016-04-29 17:29 ` Doug Evans
2016-04-29 20:40 ` Tom Tromey
2016-04-29 20:54 ` Simon Marchi
2016-04-29 21:09 ` Tom Tromey
2016-05-03 15:58 ` Yao Qi
2016-04-27 20:36 ` [PATCH v2 5/8] Add support for the Rust language Tom Tromey
2016-04-27 21:27 ` [PATCH v2 0/8] Add Rust language support Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83inz2xr82.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox