From: Pedro Alves <palves@redhat.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] completer test [was Re: [RFC] Cleanup for make_source_files_completion_list]
Date: Thu, 16 May 2013 09:38:00 -0000 [thread overview]
Message-ID: <5194A913.3050704@redhat.com> (raw)
In-Reply-To: <519427DD.3080001@earthlink.net>
On 05/16/2013 01:27 AM, Stan Shebs wrote:
> It may even be that gdb_test_multiple suffices for all of the existing
> send_gdb/gdb_expect pairs, but I don't imagine anyone has the fortitude
> to work through every one of them. :-)
Michael Snyder went through a lot of them in 2010. E.g.,
2010-06-02 Michael Snyder <msnyder@vmware.com>
* gdb.trace/actions.exp: Use gdb_test_no_output.
* gdb.trace/circ.exp: Ditto.
* gdb.trace/packetlen.exp: Ditto.
* gdb.trace/save-trace.exp: Ditto.
...
2010-05-28 Michael Snyder <msnyder@vmware.com>
* gdb.reverse/break-precsave.exp:
Replace uses of send_gdb / gdb_expect.
* gdb.reverse/break-reverse.exp:
...
(many others)
We have a lot less remaining uses of gdb_expect in tests since, but
we do still have many more than I expected. I'm a bit surprised;
I thought we had fewer:
early 2010 tree:
$ find . -name "*.exp" | grep -v "lib/" | xargs grep gdb_expect | wc -l
1849
vs current tree:
$ find . -name "*.exp" | grep -v "lib/" | xargs grep gdb_expect | wc -l
739
--
Pedro Alves
next prev parent reply other threads:[~2013-05-16 9:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 19:46 [RFC] Cleanup for make_source_files_completion_list Keith Seitz
2013-05-09 20:58 ` Tom Tromey
2013-05-09 23:45 ` Doug Evans
2013-05-13 18:42 ` Keith Seitz
2013-05-13 21:11 ` Keith Seitz
2013-05-15 17:36 ` Keith Seitz
2013-05-15 19:32 ` [RFA] completer test [was Re: [RFC] Cleanup for make_source_files_completion_list] Keith Seitz
2013-05-15 20:01 ` Tom Tromey
2013-05-15 21:22 ` Keith Seitz
2013-05-15 22:33 ` Sergio Durigan Junior
2013-05-15 23:47 ` Keith Seitz
2013-05-16 0:21 ` Sergio Durigan Junior
2013-05-16 0:27 ` Stan Shebs
2013-05-16 9:38 ` Pedro Alves [this message]
2013-05-16 5:30 ` Joel Brobecker
2013-05-16 5:49 ` Joel Brobecker
2013-05-16 15:41 ` Keith Seitz
2013-05-17 5:14 ` Joel Brobecker
2013-05-17 16:27 ` Tom Tromey
2013-05-20 5:28 ` Joel Brobecker
2013-05-20 14:47 ` Tom Tromey
2013-05-21 5:43 ` Checked in: " Joel Brobecker
2013-05-21 5:44 ` Joel Brobecker
2013-05-16 5:53 ` Sergio Durigan Junior
2013-05-16 6:00 ` Joel Brobecker
2013-05-16 9:19 ` Pedro Alves
2013-05-16 9:26 ` Joel Brobecker
2013-05-16 10:18 ` 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=5194A913.3050704@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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