From: Benjamin Kosnik <bkoz@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdb.c++ testsuite 1.1: member_data.exp (resend)
Date: Tue, 28 May 2002 09:03:00 -0000 [thread overview]
Message-ID: <20020528085943.3c2b843e.bkoz@redhat.com> (raw)
In-Reply-To: <200205272140.g4RLeuC03933@duracef.shout.net>
> member_data.exp => m-data.exp
> member_data.cc => m-data.cc
> member_data_static.exp => m-static.exp
> member_data_static.cc => m-static.cc
You are certainly willing to shape this into the form most correct for
the gdb testsuites.
> Next, I changed all the send_gdb/gdb_expect commands to gdb_test,
> which shrinks the tests considerably.
Ok.
> All the tests PASS on all my configurations (native i686-pc-linux-gnu,
> six gcc's, -gdwarf-2 and -gstabs+).
Great.
> This is a very nice test. I'm committing it shortly.
Thanks.
next prev parent reply other threads:[~2002-05-28 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 14:47 Michael Elizabeth Chastain
2002-05-28 9:03 ` Benjamin Kosnik [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-27 14:59 Michael Elizabeth Chastain
2002-05-27 10:58 Michael Elizabeth Chastain
2002-05-27 6:26 Benjamin Kosnik
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=20020528085943.3c2b843e.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.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