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 target/114839] g++-linked FreeBSD static binaries abort upon exception
Date: Wed, 24 Apr 2024 20:29:03 +0000	[thread overview]
Message-ID: <bug-114839-4-W2UO6C3vBZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114839-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114839

--- Comment #4 from Ed Maste <emaste at freebsd dot org> ---
Thanks - 54568 adds some good context. Based on that I think it may that frame
registration calls are not present in the FreeBSD crt bits used for static
binaries, which could explain the differences in OSes.

We could look into adding the registration calls, but it seems that using
--eh-frame-hdr always is the best path for us.

      parent reply	other threads:[~2024-04-24 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 17:50 [Bug driver/114839] New: " emaste at freebsd dot org
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 [this message]

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-W2UO6C3vBZ@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: link
Be 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).