[Bug gdb/31369] [gdb] command aborted with debug frame

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

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

--- Comment #2 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=2aaba7444679492ae9e2757d7d05ba63bd2ec3c7

commit 2aaba7444679492ae9e2757d7d05ba63bd2ec3c7
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon Feb 26 15:31:34 2024 +0100

    [gdb] Fix "value is not available" with debug frame

    On arm-linux, with a started hello world, running "info frame" works fine,
but
    when I set debug frame to on, I run into:
    ...
    (gdb) info frame
      ...
    [frame] frame_unwind_register_value: exit
    value is not available
    (gdb)
    ...

    The problem is here in frame_unwind_register_value:
    ...
              if (value->lazy ())
                gdb_printf (&debug_file, " lazy");
              else
                {
                  int i;
                  gdb::array_view<const gdb_byte> buf = value->contents ();
    ...
    where we call value->contents () while !value->entirely_available ().

    Fix this by checking value->entirely_available () and printing:
    ...
        [frame] frame_unwind_register_value:   -> register=91 unavailable
    ...

    Tested on arm-linux.

    PR gdb/31369
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31369

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