From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 63AA43854835; Tue, 7 Mar 2023 00:33:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 63AA43854835 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1678149190; bh=rFIvVadmz7yIxWxOS3Bi2/1ZBQYbwJi0dGPTxuNHfFk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Uepik8dAqhRSa26xuX8Ep6a2J8LVJb2AXBBrQQ2+ztnpcaoxrswJF2+dqBl2or1dr AGwndMrPevck/Bh3eI9H8ZApVBLSNlJo3LSXD74PV0zZ35Eqpq+N+TtGic+Z8vPJhM FoHC8GA+mTa1CwU7M13naf2jSe9tmC4b0PkciFyM= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/29168] [gdb/UB] gdb/dwarf2/read.c:17545:20:runtime error: shift exponent 127 is too large for 64-bit type 'long unsigned int' Date: Tue, 07 Mar 2023 00:33:08 +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: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 14.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution cc target_milestone 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=3D29168 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED CC| |tromey at sourceware dot o= rg Target Milestone|--- |14.1 --- Comment #2 from Tom Tromey --- I think this was fixed by: commit b70bff5ea52550c7cd48af7579a75ac2624ec13d Author: Simon Marchi Date: Fri Jan 20 11:51:54 2023 -0500 gdb/dwarf: fix UBsan crash in read_subrange_type I think this went in on master but not gdb-13. --=20 You are receiving this mail because: You are on the CC list for the bug.=