From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 99A1E3858D37; Sun, 14 Apr 2024 18:03:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 99A1E3858D37 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1713117832; bh=i6gh+frT3MUxPTkj3tZG0zgZBIB6n4SM/+Nw9qNs2pA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aXT+jxFE8BlWBoO5ncO5G4G6qDObZgti8T8bea1DJCF72cwQ7WkqbgG0B7aN4b0DV QRQlIjBebmdVYvUnWWq+ajTev3MVVNBjSEWakuGsR7YbrYKxSTIBYw50jCZpYlC1/8 RkR9EZwH0y1LxbU+JuUoU+020OF8+VcDh4jaI/JA= From: "brobecker at gnat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/31268] gdb.base/unwind-on-each-insn-amd64.exp regression Date: Sun, 14 Apr 2024 18:03:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: brobecker at gnat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 15.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: 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: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31268 Joel Brobecker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brobecker at gnat dot com --- Comment #9 from Joel Brobecker --- Hi Tom, > I'd like the fix for this PR to be included in the 15.1 release. For the record, can you say which consideration(s?) made you reach this assessment?=20 Looking at the fix, and in particular the title of the fix (out of bounds a= rray access), I'm guessing that the out-of-bound condition is considered sufficiently critical that the fix should be in the release. --=20 You are receiving this mail because: You are on the CC list for the bug.=