public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tromey@adacore.com>,
	 Andrew Burgess <aburgess@redhat.com>,
	Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Do not record a rejected target description
Date: Thu, 16 Feb 2023 12:20:25 -0700	[thread overview]
Message-ID: <87zg9do1s6.fsf@tromey.com> (raw)
In-Reply-To: <d73b56f9-08c5-9ce7-aced-9dfe1cd3e9aa@simark.ca> (Simon Marchi's message of "Wed, 15 Feb 2023 16:19:08 -0500")

Simon> I see:

Simon>   maint print c-tdesc^M
Simon>   There is no target description to print.^M
Simon>   (gdb) FAIL: gdb.xml/maint_print_struct.exp: printing tdesc with a structure and a bitfield

Here's a patch that avoids this problem.
Let me know what you think.

Tom

commit a12897d22ccc1d927960fa411b99723d76620af0
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Feb 16 12:17:50 2023 -0700

    Fix regression in maint_print_struct.exp
    
    An earlier patch of mine caused a regression in
    maint_print_struct.exp.  This patch fixes it by modifying the test so
    that it does not rely on the erroneous target description being
    available.

diff --git a/gdb/testsuite/gdb.xml/maint_print_struct.exp b/gdb/testsuite/gdb.xml/maint_print_struct.exp
index 6f411895501..5b7c1489d3e 100644
--- a/gdb/testsuite/gdb.xml/maint_print_struct.exp
+++ b/gdb/testsuite/gdb.xml/maint_print_struct.exp
@@ -21,12 +21,7 @@ require allow_xml_test
 
 gdb_start
 
-# Required registers are not present so it is expected a warning.
-#
-gdb_test "set tdesc filename $srcdir/$subdir/maint_print_struct.xml" "
-warning:.*" "setting a new tdesc having only a structure"
-
-gdb_test "maint print c-tdesc" "
+gdb_test "maint print c-tdesc $srcdir/$subdir/maint_print_struct.xml" "
 .*tdesc_create_reg \\(feature, \"bad_reg1\", \[0-9\]+, 1, NULL, 128, \"two_fielded\"\\);\r
 .*tdesc_create_reg \\(feature, \"bad_reg2\", \[0-9\]+, 1, NULL, 64, \"bitfield\"\\);\r
 .*" "printing tdesc with a structure and a bitfield"

  parent reply	other threads:[~2023-02-16 19:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 19:33 Tom Tromey
2023-02-14 15:16 ` Tom Tromey
2023-02-14 15:48 ` Andrew Burgess
2023-02-14 17:27   ` Tom Tromey
2023-02-15 12:56     ` Andrew Burgess
2023-02-15 15:59       ` Tom Tromey
2023-02-15 21:19         ` Simon Marchi
2023-02-15 21:38           ` Tom Tromey
2023-02-16 19:20           ` Tom Tromey [this message]
2023-02-16 19:33             ` Simon Marchi
2023-02-17 10:19             ` Andrew Burgess
2023-02-17 14:09               ` Tom Tromey
2023-02-17 22:29                 ` Andrew Burgess

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=87zg9do1s6.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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).