[Bug python/31437] [gdb/python] Unavailable register breaks python unwinding

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #4 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=306361f0687a60b06503a2df3c0ba949afca215f

commit 306361f0687a60b06503a2df3c0ba949afca215f
Author: Tom de Vries <tdevries@suse.de>
Date:   Tue Mar 19 10:30:36 2024 +0100

    [gdb] Further fix "value is not available" with debug frame

    In commit 2aaba744467 ("[gdb] Fix "value is not available" with debug
frame")
    I fixed a case in frame_unwind_register_value where using "set debug frame
on"
    caused an "info frame" command to abort, reporting a "value is not
available"
    error, due to the tpidruro register being unavailable.

    Subsequently, commit bbb12eb9c84 ("gdb/arm: Remove tpidruro register from
    non-FreeBSD target descriptions") removed the unavailable register, which
    caused a progression on test-case gdb.base/inline-frame-cycle-unwind.exp.

    While investigating the progression (see PR python/31437), I found that the
    "debug frame" output of the test-case (when reverting commit bbb12eb9c84)
    showed a smilar problem:
    ...
    Python Exception <class 'gdb.error'>: value is not available^M
    ...
    that was absent without "debug frame".

    Fix this likewise in fetch_lazy_register, and update the test-case to check
    for the exception.

    Furthermore, I realized that there's both value::entirely_available and
    value::entirely_unavailable, and that commit 2aaba744467 handled the case
    of !entirely_available by printing unavailable.

    Instead, print:
    - "unavailable" for entirely_unavailable, and
    - "partly unavailable" for !entirely_unavailable && !entirely_available.

    Tested on x86_64-linux and arm-linux.

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