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 python/31441] New: [gdb/python] Add gdb.Value.entirely_available and gdb.Value.entirely_unavailable
Date: Sat, 02 Mar 2024 08:01:32 +0000	[thread overview]
Message-ID: <bug-31441-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31441
           Summary: [gdb/python] Add gdb.Value.entirely_available and
                    gdb.Value.entirely_unavailable
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Before this commit:
...
commit bbb12eb9c84aa2b32480b7c022c494c2469ef717
Author: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Date:   Mon Feb 26 19:11:45 2024 -0300

    gdb/arm: Remove tpidruro register from non-FreeBSD target descriptions

...
test-case gdb.base/inline-frame-cycle-unwind.exp failed on arm-linux.

I managed to write a test-case fix:
...
diff --git a/gdb/testsuite/gdb.base/inline-frame-cycle-unwind.py
b/gdb/testsuite/gdb.base/inline-frame-cycle-unwind
.py
index 278fa857d5d..0110fc74276 100644
--- a/gdb/testsuite/gdb.base/inline-frame-cycle-unwind.py
+++ b/gdb/testsuite/gdb.base/inline-frame-cycle-unwind.py
@@ -65,6 +65,13 @@ class TestUnwinder(Unwinder):

         for reg in pending_frame.architecture().registers("general"):
             val = pending_frame.read_register(reg)
+            have_bytes = True
+            try:
+                val.bytes
+            except Exception:
+                have_bytes = False
+            if not have_bytes:
+                continue
             unwinder.add_saved_register(reg, val)
         return unwinder
...
which made we wonder why we have gdb.Value.is_optimized_out, but not the
is_entirely_available or is_entirely_unavailable variants.

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

             reply	other threads:[~2024-03-02  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02  8:01 vries at gcc dot gnu.org [this message]
2024-03-02  8:57 ` [Bug python/31441] " vries at gcc dot gnu.org
2024-03-02  8:58 ` 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-31441-4717@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).