Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: GDB internals manual: explain how to run selected tests
Date: Wed, 25 Jan 2006 19:57:00 -0000	[thread overview]
Message-ID: <uslrcdqtv.fsf@gnu.org> (raw)
In-Reply-To: <8f2776cb0601251040x58a6b12cg99c12e3b695d7d55@mail.gmail.com> 	(message from Jim Blandy on Wed, 25 Jan 2006 10:40:09 -0800)

> 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.


  reply	other threads:[~2006-01-25 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-25 18:40 Jim Blandy
2006-01-25 19:57 ` Eli Zaretskii [this message]
2006-01-25 21:16   ` Jim Blandy

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=uslrcdqtv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@red-bean.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