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 18:05:49 +0000 [thread overview]
Message-ID: <bug-114839-4-16opK0fEJV@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 #3 from Ed Maste <emaste at freebsd dot org> ---
(In reply to Andrew Pinski from comment #2)
> Is it the case that unwinder from LLVM needs a .eh_frame_hdr for static
> binaries while GCC's libgcc one does not?
That's possible, but in the investigation in the FreeBSD bug report I believe
that GCC's libgcc is being used here:
#0 0x00000000004d4dca in thr_kill ()
#1 0x00000000004c226f in raise ()
#2 0x00000000004df6f9 in abort ()
#3 0x0000000000402bef in uw_init_context_1 (
context=context@entry=0x7fffdfffdd50,
outer_cfa=outer_cfa@entry=0x7fffdfffdf80,
outer_ra=0x4b2326 <thread_unwind+54>)
at ../../../gcc-13.2.0/libgcc/unwind-dw2.c:1336
#4 0x00000000004ad986 in _Unwind_ForcedUnwind (exc=0x800818940,
stop=0x4b24d0 <thread_unwind_stop>, stop_argument=0x0)
at ../../../gcc-13.2.0/libgcc/unwind.inc:212
next prev parent reply other threads:[~2024-04-24 18:05 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 [this message]
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-16opK0fEJV@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).