Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>,
	Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [committed][gdb/testsuite] Disable vgdb tests if xml not supported
Date: Thu, 30 Sep 2021 23:47:12 +0200	[thread overview]
Message-ID: <d1866767-b703-4cc3-b8b7-1caac50fd6ea@suse.de> (raw)
In-Reply-To: <c39a2698-74fc-78b0-e025-cadaa953bb9e@suse.de>

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

On 9/30/21 11:41 PM, Tom de Vries wrote:
> On 9/30/21 7:30 PM, Tom Tromey wrote:
>> Tom> +if { [gdb_skip_xml_test] } {
>> Tom> +    # Valgrind gdbserver requires gdb with xml support.
>> Tom> +    return 0
>> Tom> +}
>>
>> Do we want/need an 'untested' in there?
>>
> 
> Ack, will do.
> 

Pushed this patch.

Thanks,
- Tom

[-- Attachment #2: 0001-gdb-testsuite-Add-untested-for-missing-xml-support-in-gdb.base-valgrind-.exp.patch --]
[-- Type: text/x-patch, Size: 2056 bytes --]

[gdb/testsuite] Add untested for missing xml support in gdb.base/valgrind*.exp

Add untested in case missing xml support is detected in test-cases
gdb.base/valgrind*.exp.

Tested on x86_64-linux.

---
 gdb/testsuite/gdb.base/valgrind-bt.exp        | 1 +
 gdb/testsuite/gdb.base/valgrind-disp-step.exp | 1 +
 gdb/testsuite/gdb.base/valgrind-infcall-2.exp | 1 +
 gdb/testsuite/gdb.base/valgrind-infcall.exp   | 1 +
 4 files changed, 4 insertions(+)

diff --git a/gdb/testsuite/gdb.base/valgrind-bt.exp b/gdb/testsuite/gdb.base/valgrind-bt.exp
index 4b84a45d333..440c6e403e9 100644
--- a/gdb/testsuite/gdb.base/valgrind-bt.exp
+++ b/gdb/testsuite/gdb.base/valgrind-bt.exp
@@ -15,6 +15,7 @@
 
 if { [gdb_skip_xml_test] } {
     # Valgrind gdbserver requires gdb with xml support.
+    untested "missing xml support"
     return 0
 }
 
diff --git a/gdb/testsuite/gdb.base/valgrind-disp-step.exp b/gdb/testsuite/gdb.base/valgrind-disp-step.exp
index f9429fbd69a..88ac848ae2d 100644
--- a/gdb/testsuite/gdb.base/valgrind-disp-step.exp
+++ b/gdb/testsuite/gdb.base/valgrind-disp-step.exp
@@ -20,6 +20,7 @@
 
 if { [gdb_skip_xml_test] } {
     # Valgrind gdbserver requires gdb with xml support.
+    untested "missing xml support"
     return 0
 }
 
diff --git a/gdb/testsuite/gdb.base/valgrind-infcall-2.exp b/gdb/testsuite/gdb.base/valgrind-infcall-2.exp
index 30881ca72ea..a368717c1e8 100644
--- a/gdb/testsuite/gdb.base/valgrind-infcall-2.exp
+++ b/gdb/testsuite/gdb.base/valgrind-infcall-2.exp
@@ -31,6 +31,7 @@
 
 if { [gdb_skip_xml_test] } {
     # Valgrind gdbserver requires gdb with xml support.
+    untested "missing xml support"
     return 0
 }
 
diff --git a/gdb/testsuite/gdb.base/valgrind-infcall.exp b/gdb/testsuite/gdb.base/valgrind-infcall.exp
index 0108f92ceaf..9f49a320f52 100644
--- a/gdb/testsuite/gdb.base/valgrind-infcall.exp
+++ b/gdb/testsuite/gdb.base/valgrind-infcall.exp
@@ -15,6 +15,7 @@
 
 if { [gdb_skip_xml_test] } {
     # Valgrind gdbserver requires gdb with xml support.
+    untested "missing xml support"
     return 0
 }
 

  reply	other threads:[~2021-09-30 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 13:55 Tom de Vries via Gdb-patches
2021-09-30 17:30 ` Tom Tromey
2021-09-30 21:41   ` Tom de Vries via Gdb-patches
2021-09-30 21:47     ` Tom de Vries via Gdb-patches [this message]
2021-10-05 18:15     ` Tom Tromey
2021-10-06  7:40       ` [PATCH][gdb/testsuite] Add proc require in lib/gdb.exp Tom de Vries via Gdb-patches
2021-10-07 11:00         ` [PATCH][gdb/testsuite] Prevent compilation fails with unix/-fPIE/-pie Tom de Vries via Gdb-patches
2021-10-08 14:37           ` Tom de Vries via Gdb-patches
2021-10-11 10:28         ` [PATCH][gdb/testsuite] Add proc require in lib/gdb.exp Tom de Vries via Gdb-patches

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=d1866767-b703-4cc3-b8b7-1caac50fd6ea@suse.de \
    --to=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.com \
    /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