This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFA: GDB internals manual: explain how to run selected tests
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Jim Blandy <jimb at red-bean dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 25 Jan 2006 21:56:28 +0200
- Subject: Re: RFA: GDB internals manual: explain how to run selected tests
- References: <8f2776cb0601251040x58a6b12cg99c12e3b695d7d55@mail.gmail.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Wed, 25 Jan 2006 10:40:09 -0800
> From: Jim Blandy <jimb@red-bean.com>
>
> gdb/doc/ChangeLog:
> 2006-01-25 Jim Blandy <jimb@redhat.com>
>
> * gdbint.texinfo (Testsuite): Explain how to run selected tests.
>
> Index: gdb/doc/gdbint.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
> retrieving revision 1.235
> diff -c -p -r1.235 gdbint.texinfo
> *** gdb/doc/gdbint.texinfo 20 Jan 2006 21:58:16 -0000 1.235
> --- gdb/doc/gdbint.texinfo 25 Jan 2006 18:38:13 -0000
> *************** finished, you'll get a summary that look
> *** 6444,6449 ****
> --- 6469,6481 ----
> # of untested testcases 5
> @end smallexample
>
> + To run a specific test script, type:
> + @example
> + make check RUNTESTFLAGS='@var{tests}'
> + @end example
> + where @var{tests} is a list of test script file names, separated by
> + spaces.
> +
> The ideal test run consists of expected passes only; however, reality
> conspires to keep us from this ideal. Unexpected failures indicate
> real problems, whether in @value{GDBN} or in the testsuite. Expected
Thanks, this is approved.