From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9D6B83858D28; Wed, 3 May 2023 20:33:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9D6B83858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683145986; bh=VpgP60wqNw4H8iINHrmqj0xi9vsOLs9TuyjisZMY8h8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XT3EK5xuXHd2KTL7RM5kxn7UbXqq/P9oWN5NnPdXOy8UeMHxRbiAUrpUU+rUPLHBk sjz3jG3E5WAzdekGYkSTk/B06ejER7X5Z4eC+fv56WsIPvjAxXSgmGKbuqLhO3fc5v 17935kImQrWRgoHldRrFRaNms+m9ZHsZXPcf0c6s= From: "chergert at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109719] Truncated frame-pointer unwinding via Linux perf with g++ Date: Wed, 03 May 2023 20:33:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: chergert at redhat dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.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://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109719 --- Comment #5 from Christian Hergert --- Created attachment 54985 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D54985&action=3Dedit First level of stack traces with g++ This shows stack traces when the only change was compiling harfbuzz with g++ instead of clang++. Much of the unwinding done by the kernel becomes corrupted and shallow as y= ou can see by lots of functions which have no business being called before `_start` or `__GI__clone3` are getting called.=