public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29055] [gdb/testsuite] FAIL: gdb.ada/ghost.exp: print value (timeout)
Date: Thu, 09 Jun 2022 09:32:56 +0000	[thread overview]
Message-ID: <bug-29055-4717-K69ZyvVJEm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29055-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29055

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
How about prefixing with the package name:
...
diff --git a/gdb/testsuite/gdb.ada/ghost.exp b/gdb/testsuite/gdb.ada/ghost.exp
index 7f92b130eff..ece03dbe2f8 100644
--- a/gdb/testsuite/gdb.ada/ghost.exp
+++ b/gdb/testsuite/gdb.ada/ghost.exp
@@ -32,6 +32,6 @@ if ![runto "main.adb:$bp_location" ] then {
   return
 }

-gdb_test "print value" " = 64 '@'"
-gdb_test "print ghost_value" " = 64 '@'"
-gdb_test "print value2" " = 33 '!'"
+gdb_test "print pck.value" " = 64 '@'"
+gdb_test "print pck.ghost_value" " = 64 '@'"
+gdb_test "print gpck.value2" " = 33 '!'"
...
?

That looks like a more reliable way to get the names we want.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-06-09  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  5:44 [Bug testsuite/29055] New: " vries at gcc dot gnu.org
2022-04-14 19:09 ` [Bug testsuite/29055] " tromey at sourceware dot org
2022-06-09  9:32 ` vries at gcc dot gnu.org [this message]
2022-06-09 22:01 ` tromey at sourceware dot org
2022-06-10  6:48 ` vries at gcc dot gnu.org

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=bug-29055-4717-K69ZyvVJEm@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).