public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] [gdb/testsuite] Remove unnecessary warning in gdb.base/default.exp
Date: Fri,  7 Oct 2022 14:17:55 +0000 (GMT)	[thread overview]
Message-ID: <20221007141755.84E01382F980@sourceware.org> (raw)

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

commit 8c7cb01a296c3f91372505b67be76ca41f0665a6
Author: Tom de Vries <tdevries@suse.de>
Date:   Fri Oct 7 16:17:35 2022 +0200

    [gdb/testsuite] Remove unnecessary warning in gdb.base/default.exp
    
    When running test-case gdb.base/default.exp with target board
    native-gdbserver, we get:
    ...
    WARNING: Skipping backtrace and break tests because of GDB stub.
    ...
    
    There's no need for such a warning, so remove it.
    
    Tested on x86_64-linux with native and target board native-gdbserver.

Diff:
---
 gdb/testsuite/gdb.base/default.exp | 2 --
 1 file changed, 2 deletions(-)

diff --git a/gdb/testsuite/gdb.base/default.exp b/gdb/testsuite/gdb.base/default.exp
index e1e0d311b6c..29e76642830 100644
--- a/gdb/testsuite/gdb.base/default.exp
+++ b/gdb/testsuite/gdb.base/default.exp
@@ -66,8 +66,6 @@ if !$use_gdb_stub {
     foreach i "bt ba bac" {
 	gdb_test $i "No stack." "backtrace \"$i\" abbreviation"
     }
-} else {
-    warning "Skipping backtrace and break tests because of GDB stub."
 }
 
 gdb_test "continue" "The program is not being run."

                 reply	other threads:[~2022-10-07 14:17 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=20221007141755.84E01382F980@sourceware.org \
    --to=vries@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).