public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb/testsuite: small cleanup in mi-break-qualified.exp
Date: Tue,  3 May 2022 09:49:03 +0000 (GMT)	[thread overview]
Message-ID: <20220503094903.87D443858C51@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3cd25174b88a10474131573dda6c15d09cb3031e

commit 3cd25174b88a10474131573dda6c15d09cb3031e
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Fri Apr 29 18:07:54 2022 +0100

    gdb/testsuite: small cleanup in mi-break-qualified.exp
    
    It is not necessary to pass an empty string to mi_gdb_start, passing
    the empty string is equivalent to passing no arguments, which is what
    we do everywhere else (that we don't need to specify an actual
    argument).
    
    The only place we use 'mi_gdb_start ""' is in
    gdb.mi/mi-break-qualified.exp, so in this commit I just replace that
    with a call to 'mi_gdb_start' - just for consistency.
    
    There should be no change in what is tested after this commit.

Diff:
---
 gdb/testsuite/gdb.mi/mi-break-qualified.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.mi/mi-break-qualified.exp b/gdb/testsuite/gdb.mi/mi-break-qualified.exp
index ff37950fd76..ca6df0782df 100644
--- a/gdb/testsuite/gdb.mi/mi-break-qualified.exp
+++ b/gdb/testsuite/gdb.mi/mi-break-qualified.exp
@@ -95,7 +95,7 @@ proc test_break_qualified {} {
 
 mi_gdb_exit
 
-if [mi_gdb_start ""] {
+if [mi_gdb_start] {
     return
 }


                 reply	other threads:[~2022-05-03  9:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220503094903.87D443858C51@sourceware.org \
    --to=aburgess@sourceware.org \
    --cc=gdb-cvs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).