From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CCFBC38582B0; Tue, 7 Mar 2023 16:16:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CCFBC38582B0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678205793; bh=+QdigX5UUWqKo4GdSvyWg2Ci17wdegGkFjaBnmdVTd4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Yd8lc5z77KXNZywDCaMlKynmhnNZQTlyZ1Nn/8tSvfgApcc32fRQuY+Ty7EouedHz iRk/8jDFqQd3rJV8f1ER6Pt+OHcCIsCuV/Vz70vNqkIpoH2RKXY3W+O1XyVhFcsbz9 rYOprk5TcuujN2IlCXtzAtmo/cw/C1H1eYpIhmas= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/109054] _Unwind_GetLanguageSpecificData should have protected visibility Date: Tue, 07 Mar 2023 16:16:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgcc X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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=3D109054 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fw at gcc dot gnu.org --- Comment #2 from Jakub Jelinek --- On the other side, it is true that the unwind-dw2{,_s}.o entrypoints (or at least their majority) uses struct _Unwind_Context which is implementation specific and so using some other one is likely incorrect (in theory one cou= ld wrap it around and just use dlsym (RTLD_NEXT, "_Unwind_*") found entrypoints under the hood with some extra code). Things are even more complicated by libgcc being configurable to use libunw= ind and just call __libunwind_* APIs under the hood (on by default only on ia64-hpux but there is configure option for it elsewhere). Though, I wonder how can unwinding work properly even if we did that. Because e.g. libstdc++.so.6 (or libsupc++.a) C++ EH personality routine cal= ls various _Unwind_* APIs too, including _Unwind_GetLanguageSpecificData, _Unwind_GetGR, _Unwind_GetIP*, _Unwind_GetRegionStart, so if it gets some subset of those symbols from a different unwinder, it can't work correctly.=