From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B8A9D3858D33; Thu, 11 Apr 2024 19:06:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B8A9D3858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1712862368; bh=QxkItceicshvDIu/HpB/kptMlZDTB9UT3O70OSwzWO4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=fj8o/5vJR/PFkeZwPeDuyfRD5lUl3QNba63xZC7I2NzO5cX+bE/+tbxvVaVk/apQ9 OliOVuRYWl2bSBJuxanA0G3yy1vXwVefyZiKe24bmcihIV6t7s1T1T5zRF2nK1jOF+ ozE5JRa2RGWHOhjmj5DXM/UnHSuk8JKUc8QeuOzc= From: "blarsen at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/31352] [gdb/cli, recursive internal problem] sig_write uses gdb_stderr, which may be a string_file, which doesn't support write_async_safe Date: Thu, 11 Apr 2024 19:06:07 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: blarsen at redhat 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: --- 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=3D31352 Guinevere Larsen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blarsen at redhat dot com --- Comment #1 from Guinevere Larsen --- I've come across this same bug while trying to debug a segfault from my frame_unwind move to classes[1] on 32-bit arm, no changes required to internal_vproblem or quit function. If you stop inside frame_unwind_legacy::sniffer and send a segfault to inner GDB, you can trigger the situation where internal_verror is writing to a gdb_stderr that doesn't have write_async_safe. [1] https://inbox.sourceware.org/gdb-patches/20240408201915.1482831-4-blarsen@r= edhat.com/T/#u --=20 You are receiving this mail because: You are on the CC list for the bug.=