public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Poulhies <mpoulhies@kalrayinc.com>
To: Marc Poulhies <mpoulhies@kalrayinc.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	libstdc++ <libstdc++@gcc.gnu.org>, Luc Michel <lmichel@kalray.eu>
Subject: Re: [NEWS]  libstdc++: Fix testsuite for skipping gdb tests on remote/non-native target
Date: Wed, 21 Jul 2021 17:02:24 +0200 (CEST)	[thread overview]
Message-ID: <291496446.934555.1626879744068.JavaMail.zimbra@kalray.eu> (raw)
In-Reply-To: <1855720815.793351.1626790336484.JavaMail.zimbra@kalray.eu>

[-- Attachment #1: Type: text/plain, Size: 797 bytes --]

With the correct patch attached, sorry for the incorrect previous one !

Marc

----- Original Message -----
> From: "gcc-patches" <gcc-patches@gcc.gnu.org>
> To: "gcc-patches" <gcc-patches@gcc.gnu.org>, "libstdc++" <libstdc++@gcc.gnu.org>
> Cc: "Luc Michel" <lmichel@kalray.eu>
> Sent: Tuesday, July 20, 2021 4:12:16 PM
> Subject: [NEWS]  libstdc++: Fix testsuite for skipping gdb tests on remote/non-native target

> This fixes an incorrect invocation of gdb on remote targets where DejaGNU would
> try to run host's gdb in remote target simulator.
> gdb-test skips the testing when target is remote or non native but the gdb
> version check function does not.
> 
> libstdc++-v3/ChangeLog:
>        * testsuite/lib/gdb-test.exp (gdb_batch_check): Exit if non native or remote
>         target.



[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch; name=patch.txt, Size: 608 bytes --]

diff --git a/libstdc++-v3/testsuite/lib/gdb-test.exp b/libstdc++-v3/testsuite/lib/gdb-test.exp
index af20c85e5a0..0ec9ac46c68 100644
--- a/libstdc++-v3/testsuite/lib/gdb-test.exp
+++ b/libstdc++-v3/testsuite/lib/gdb-test.exp
@@ -244,6 +244,8 @@ proc gdb-test { marker {selector {}} {load_xmethods 0} } {
 
 # Invoke gdb with a command and pattern-match the output.
 proc gdb_batch_check {command pattern} {
+    if { ![isnative] || [is_remote target] } { return 0 }
+
     set gdb_name $::env(GUALITY_GDB_NAME)
     set cmd "$gdb_name -nw -nx -quiet -batch -ex \"$command\""
     send_log "Spawning: $cmd\n"

  reply	other threads:[~2021-07-21 15:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 14:12 Marc Poulhies
2021-07-21 15:02 ` Marc Poulhies [this message]
2021-07-21 15:53   ` [NEWS] " Jonathan Wakely
2021-07-22  9:19     ` Marc Poulhies

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=291496446.934555.1626879744068.JavaMail.zimbra@kalray.eu \
    --to=mpoulhies@kalrayinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=lmichel@kalray.eu \
    /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).