public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "emaste at freebsd dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/114839] New: g++-linked FreeBSD static binaries abort upon exception Date: Wed, 24 Apr 2024 17:50:31 +0000 [thread overview] Message-ID: <bug-114839-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114839 Bug ID: 114839 Summary: g++-linked FreeBSD static binaries abort upon exception Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: emaste at freebsd dot org Target Milestone: --- When compiling and statically linking a binary on FreeBSD with GCC the EH_FRAME segment is omitted, and then libgcc's exception unwinder aborts when it cannot find the EH_FRAME segment. See FreeBSD bug report https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278551 for full details and history. From -dumpspecs it looks like (assuming I understand correctly) that --eh-frame-header is not passed when static is specified: ... *link: %{!static|static-pie:--eh-frame-hdr} %{m32:-m elf_i386_fbsd}%{!m32:-m elf_x86_64_fbsd} %{p:%nconsider using '-pg' instead of '-p' with gprof(1)} %{v:-V} %{assert*} %{R*} %{rpath*} %{defsym*} %{shared:-Bshareable %{h*} %{soname*}} %{!shared: %{!static: %{rdynamic:-export-dynamic} -dynamic-linker %(fbsd_dynamic_linker) } %{static:-Bstatic}} %{symbolic:-Bsymbolic}
next reply other threads:[~2024-04-24 17:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-24 17:50 emaste at freebsd dot org [this message] 2024-04-24 17:55 ` [Bug target/114839] " pinskia at gcc dot gnu.org 2024-04-24 18:01 ` pinskia at gcc dot gnu.org 2024-04-24 18:05 ` emaste at freebsd dot org 2024-04-24 20:29 ` emaste at freebsd dot org
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-114839-4@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).