public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Incorrect unwind when throwing exceptions - possible cause?
Date: Fri, 4 Feb 2022 10:37:52 +0000	[thread overview]
Message-ID: <bc276231-a585-f4ef-858e-f3c873ac400c@redhat.com> (raw)
In-Reply-To: <CAEPqvox8mCqyK-pbXXX3scw2iZx_=iRynaD9aUDMbN-FF7W4rA@mail.gmail.com>

On 2/3/22 15:38, Juraj Oršulić wrote:
> Just to confirm, the problem was solved by adjusting the 3rdparty library
> guilty for pulling in libunwind (in our case, Google glog, which has it as
> an optional dependency) and evicting libunwind from the link list
> (and using gcc's builtin unwinder instead).
> 
> It looks like that an up-to-date libunwind on Arch as of today doesn't have
> this bug, but it's certainly present on Ubuntu 20.04.
> 
> Thanks again Florian!

Yes, I agree, that was a great catch.

-- 
Andrew Haley  (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671


      reply	other threads:[~2022-02-04 10:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  0:43 Juraj Oršulić
2022-02-03  1:06 ` Sam Varshavchik
2022-02-03  1:36 ` Juraj Oršulić
2022-02-03  2:15   ` Juraj Oršulić
2022-02-03 11:39 ` Florian Weimer
     [not found]   ` <CAEPqvowbo+iH4dazsfub3Vjc1D_zFGgKv2tg92Kv32vGVTq-2w@mail.gmail.com>
     [not found]     ` <87wnict9uz.fsf@oldenburg.str.redhat.com>
2022-02-03 13:40       ` Juraj Oršulić
2022-02-03 15:38         ` Juraj Oršulić
2022-02-04 10:37           ` Andrew Haley [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=bc276231-a585-f4ef-858e-f3c873ac400c@redhat.com \
    --to=aph@redhat.com \
    --cc=gcc-help@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).