From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 051DA3858C39; Mon, 26 Feb 2024 14:31:32 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 051DA3858C39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1708957893;
	bh=4il9NtWjwjSTsZBUN52ysbotlU77l+16XqxmP3WXO3Q=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=JV7kJj2h9PzCNTOUbB/uXJxlwSdb2xdceO/Gm4Xlpe2uYH19NlgpZ6oMSXRTp5wQ8
	 LZ8SQ2BOwdeA9i/KSTJtEdH9ZNXMTICSUd6kOafJbnzdtY3Me6BGeZLfulptdg3RsM
	 3dAgJrAEvEdyx3o/f5+kD0dMFfAYH3LGyJ5+Up+U=
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31369] [gdb] command aborted with debug frame
Date: Mon, 26 Feb 2024 14:31:31 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-31369-4717-muq8LKpzJy@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-31369-4717@http.sourceware.org/bugzilla/>
References: <bug-31369-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

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

--- 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=3Dbinutils-gdb.git;h=3D2aaba7444679=
492ae9e2757d7d05ba63bd2ec3c7

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 fi=
ne,
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 =3D 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=3D91 unavailable
    ...

    Tested on arm-linux.

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

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