From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1B7D23858D32; Thu, 13 Apr 2023 20:00:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1B7D23858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1681416022; bh=ru/ruTatQFmSgBn4Ea+OSwj1Df720mYjkSfzI/lv+g0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RH0Tf7uJvH7RMPsynP6V0Xbkdc9Uy7mrVC5TuvXJE+eAKOcw58dZhc+4/tN+eehkk +gBqYvsGwc1Qemj3spLD0o7sJgXwumrF8ZhVbZ0xxEnZcbtTRqX8kC7fxJdlUdGhMl +0Itl+Z5tete0hR8BmP6wRen0nNbtb/DKbyKi7zQ= From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/29257] Double free of demangled symbol name Date: Thu, 13 Apr 2023 20:00:21 +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: 10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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=3D29257 --- Comment #14 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Df96328accde1= e6302b62aa880675594618079cb3 commit f96328accde1e6302b62aa880675594618079cb3 Author: Tom Tromey Date: Tue Dec 6 12:07:12 2022 -0700 Avoid double-free with debuginfod PR gdb/29257 points out a possible double free when debuginfod is in use. Aside from some ugly warts in the symbol code (an ongoing issue), the underlying issue in this particular case is that elfread.c seems to assume that symfile_bfd_open will return NULL on error, whereas in reality it throws an exception. As this code isn't prepared for an exception, bad things result. This patch fixes the problem by introducing a non-throwing variant of symfile_bfd_open and using it in the affected places. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29257 --=20 You are receiving this mail because: You are on the CC list for the bug.=