[Bug exp/31231] [gdb, ppc64le] frame.c:2088: internal-error: get_next_frame_sentinel_okay: Assertion `!is_sentinel_frame_id (this_frame->this_id.value)' failed.

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

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

--- Comment #5 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Simon Marchi <simark@sourceware.org>:

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

commit 47ff07a6c283a39fa3b8c92d823c8851678dfc0f
Author: Simon Marchi <simon.marchi@efficios.com>
Date:   Thu Jan 11 11:41:04 2024 -0500

    gdb: fix frame passed to gdbarch_value_to_register in value_assign

    Commit 78f2fd84e83 ("gdb: remove VALUE_REGNUM, add value::regnum")
    introduced an unexpected change in value_assign.  It replaced
    `get_prev_frame_always (next_frame)` with `next_frame`in the call to
    gdbarch_value_to_register.

    This is the result of a merge error, since I previously had a patch to
    change gdbarch_value_to_register to take the next frame, and later
    decided to drop it.  Revert that change.

    Add a test based on the DWARF assembler to expose the problem and test
    the fix.  I also tested on ppc64le to make sure the problem reported in
    PR 31231 was fixed.

    Change-Id: Ib8b851287ac27a4b2e386f7b680cf65865e6aee6
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31231

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