This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] gdb.dwarf2, gdb.gdb, gdb.multi, gdb.opt, use gdb_test_no_output
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Michael Snyder <msnyder at vmware dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Wed, 2 Jun 2010 14:31:35 -0700
- Subject: Re: [RFA] gdb.dwarf2, gdb.gdb, gdb.multi, gdb.opt, use gdb_test_no_output
- References: <4C06BC3B.7070500@vmware.com>
> 2010-06-02 Michael Snyder <msnyder@msnyder-server.eng.vmware.com>
>
> * gdb.dwarf2/dw2-basic.exp: Use gdb_test_no_output.
> * gdb.dwarf2/dw2-compressed.exp: Ditto.
> * gdb.dwarf2/dw2-intercu.exp: Ditto.
> * gdb.dwarf2/dw2-intermix.exp: Ditto.
> * gdb.dwarf2/dw2-producer.exp: Ditto.
> * gdb.dwarf2/mac-fileno.exp: Ditto.
>
> * gdb.gdb/observer.exp: Use gdb_test_no_output.
> * gdb.gdb/selftest.exp: Ditto.
>
> * gdb.multi/base.exp: Use gdb_test_no_output.
>
> * gdb.opt/inline-cmds.exp: Use gdb_test_no_output.
This is OK. Generally speaking, I think that if the test is for a "set
bla" command, the change is fairly obvious and you can commit without
approval.
--
Joel