public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/104207] [12 Regression] Crash in _Unwind_Find_FDE if object lacks unwind information Date: Tue, 25 Jan 2022 11:10:22 +0000 [thread overview] Message-ID: <bug-104207-4-xiMyVs2aFX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104207-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104207 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Florian Weimer <fw@gcc.gnu.org>: https://gcc.gnu.org/g:ab2a2457780d224343ce05e7d8e2964c6a47fd83 commit r12-6857-gab2a2457780d224343ce05e7d8e2964c6a47fd83 Author: Florian Weimer <fweimer@redhat.com> Date: Tue Jan 25 12:09:56 2022 +0100 libgcc: Fix _Unwind_Find_FDE for missing unwind data with glibc 2.35 _dl_find_object returns success even if no unwind information has been found, and dlfo_eh_frame is NULL. libgcc/ChangeLog: PR libgcc/104207 * unwind-dw2-fde-dip.c (_Unwind_Find_FDE): Add NULL check.
next prev parent reply other threads:[~2022-01-25 11:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 17:09 [Bug libgcc/104207] New: " fw at gcc dot gnu.org 2022-01-24 17:11 ` [Bug libgcc/104207] " mpolacek at gcc dot gnu.org 2022-01-24 19:08 ` fw at gcc dot gnu.org 2022-01-25 7:55 ` rguenth at gcc dot gnu.org 2022-01-25 11:07 ` fw at gcc dot gnu.org 2022-01-25 11:10 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-25 11:11 ` fw at gcc dot gnu.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-104207-4-xiMyVs2aFX@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).