public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.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 [thread overview] Message-ID: <bug-109054-4-br6PViWbcv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109054-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109054 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fw at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- 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 could 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 libunwind 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 calls 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.
next prev parent reply other threads:[~2023-03-07 16:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-07 15:39 [Bug libgcc/109054] New: " woodard at redhat dot com 2023-03-07 15:53 ` [Bug libgcc/109054] " jakub at gcc dot gnu.org 2023-03-07 16:16 ` jakub at gcc dot gnu.org [this message] 2023-03-07 17:42 ` woodard at redhat dot com 2023-03-07 17:49 ` jakub at gcc dot gnu.org 2023-03-07 17:58 ` woodard at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-109054-4-br6PViWbcv@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).