[Bug symtab/31268] gdb.base/unwind-on-each-insn-amd64.exp regression

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

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

--- Comment #11 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Bernd Edlinger <edlinger@sourceware.org>:

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

commit 63ddc8af5d7d3ad909aad66291f23507ba987bb4
Author: Bernd Edlinger <bernd.edlinger@hotmail.de>
Date:   Tue Apr 9 09:27:52 2024 +0000

    Fix an out of bounds array access in find_epilogue_using_linetable

    An out of bounds array access in find_epilogue_using_linetable causes
random
    test failures like these:

    FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6:
$fba_value == $fn_fba
    FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: check
frame-id matches
    FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: bt 2
    FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: up
    FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: $sp_value
== $::main_sp
    FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6:
$fba_value == $::main_fba
    FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: [string
equal $fid $::main_fid]

    Here the read happens below the first element of the line
    table, and the test failure depends on the value that is
    read from there.

    It also happens that std::lower_bound returns a pointer exactly at the
upper
    bound of the line table, also here the read value is undefined, that
happens
    in this test:

    FAIL: gdb.dwarf2/dw2-epilogue-begin.exp: confirm watchpoint doesn't trigger

    Fixes: 528b729be1a2 ("gdb/dwarf2: Add support for DW_LNS_set_epilogue_begin
in line-table")

    Co-Authored-By: Tom de Vries <tdevries@suse.de>

    PR symtab/31268
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31268

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