public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tneumann at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/110956] gcc_assert is hit at gcc-13.2.0/libgcc/unwind-dw2-fde.c#L291 with some special library Date: Wed, 09 Aug 2023 10:40:27 +0000 [thread overview] Message-ID: <bug-110956-4-UApcld1UF1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110956-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110956 --- Comment #1 from Thomas Neumann <tneumann at users dot sourceforge.net> --- The assert says that the code tries to de-register a frame that it did not register before or that was deregistered before. If you see that failing you might want to add some print statements to __register_frame_info_{tables_|}bases and __deregister_frame_info_bases. But the example that you included in the report does not seem to trigger the assert but crashes during unwinding instead? This has to be looked at in a debugger. I do not have access to Solaris. If you can give me remote access to a suitable machine I am willing to debug this, otherwise you must check yourself why the crash happens.
next prev parent reply other threads:[~2023-08-09 10:40 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-09 7:33 [Bug libgcc/110956] New: " sumbera at volny dot cz 2023-08-09 10:40 ` tneumann at users dot sourceforge.net [this message] 2023-08-09 11:09 ` [Bug libgcc/110956] " ro at gcc dot gnu.org 2023-08-09 11:15 ` [Bug libgcc/110956] [13, 14 regression] " ro at gcc dot gnu.org 2023-08-09 11:18 ` ro at gcc dot gnu.org 2023-08-09 13:40 ` [Bug libgcc/110956] [13/14 " rguenth at gcc dot gnu.org 2023-08-09 13:53 ` tneumann at users dot sourceforge.net 2023-08-09 17:02 ` ro at manam dot mail-host-address-is-not-set 2023-08-09 22:55 ` tneumann at users dot sourceforge.net 2023-08-10 6:49 ` tneumann at users dot sourceforge.net 2023-08-10 8:44 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-08-10 11:11 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-08-11 15:21 ` cvs-commit at gcc dot gnu.org 2023-08-11 15:29 ` cvs-commit at gcc dot gnu.org 2023-10-09 9:57 ` rguenth at gcc dot gnu.org 2024-03-10 3:46 ` law 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-110956-4-UApcld1UF1@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).