From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 31E613858C36; Wed, 13 Mar 2024 10:12:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 31E613858C36 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1710324734; bh=3bZFXi88jveeE3Y7hxddNn+zlBhnD9PegrBJ6vCB4Es=; h=From:To:Subject:Date:In-Reply-To:References:From; b=i4EBF5vbu0iy2+Ak9/czPx78Uoj3KKvzB5Z6/BzTM9GhEB3mrWLShwVVNkeyBWYAU jXSnMUlEomFoLH7aWFsw2phyPGRQLYV43Qgx9lFBnGtIrH3u6T3fHKgoAcV52sgmQC Kntav9NUXYabIt1+qXM/up2J2QbKWk8wrnUwhDkI= From: "davispuh at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/31478] GDB crashes when corrupted debuginfo Date: Wed, 13 Mar 2024 10:12:11 +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: 14.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: davispuh at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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=3D31478 --- Comment #3 from D=C4=81vis Mos=C4=81ns --- Created attachment 15402 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D15402&action=3Ded= it Crashing debuginfo (In reply to Aaron Merey from comment #2) > This may be difficult to reproduce. Do you have an environment set up wh= ere > 'gdb program' with debuginfod enabled reliably crashes when > ~/.cache/debuginfod_client is removed? No it doesn't crash if I remove `~/.cache/debuginfod_client` because issue = is purely with some corrupted file there. I now narrowed it down to ~/.cache/debuginfod_client/c0b747f77ce7222a94ecae5e362d140fb5432461/debugin= fo (attached here) I'm not sure if you can reproduce crash since it probably depends on exact program/libraries but you can try using Arch Linux, copying given debuginfo file and then running > DEBUGINFOD_URLS=3Dhttps://debuginfod.archlinux.org gdb konsole -ex "set d= ebuginfod enabled on" -ex "run" konsole is from KDE (pacman -S konsole) --=20 You are receiving this mail because: You are on the CC list for the bug.=