public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lancethepants at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105730] New: Issue with commit - Allow std::condition_variable waits to be cancelled Date: Wed, 25 May 2022 17:32:43 +0000 [thread overview] Message-ID: <bug-105730-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105730 Bug ID: 105730 Summary: Issue with commit - Allow std::condition_variable waits to be cancelled Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: lancethepants at gmail dot com Target Milestone: --- I noticed that the lld-14 linker (and also lldb) built with gcc-12 was segfaulting and pointing to libstdc++ in the backtrace. I've narrowed it down to commit 9e18a25331fa25c3907249fede65a02c6817b06e. When I reverse this commit then lld built by gcc functions again normally. gcc-12.1 release uclibc-ng c-standard library armv7 cpu I'm not sure if the issue is unique to uclibc-ng, arm, or if it's a general issue to all platforms. Here is the gdb log. Starting program: /mmc/bin/ld.lld -plugin /mmc/libexec/gcc/arm-tomatoware-linux-uclibcgnueabi/12.1.0/liblto_plugin.so -plugin-opt=/mmc/libexec/gcc/arm-tomatoware-linux-uclibcgnueabi/12.1.0/lto-wrapper -plugin-opt=-fresolution=/mmc/tmp/cc1ZwXDr.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --sysroot=/mmc --eh-frame-hdr -dynamic-linker /mmc/lib/ld-uClibc.so.1 -X -m armelf_linux_eabi -o hello /mmc/usr/lib/crt1.o /mmc/usr/lib/crti.o /mmc/lib/gcc/arm-tomatoware-linux-uclibcgnueabi/12.1.0/crtbegin.o -L/mmc/lib/gcc/arm-tomatoware-linux-uclibcgnueabi/12.1.0 -L/mmc/lib/gcc/arm-tomatoware-linux-uclibcgnueabi/12.1.0/../../../../arm-tomatoware-linux-uclibcgnueabi/lib -L/mmc/lib/gcc/arm-tomatoware-linux-uclibcgnueabi/12.1.0/../../.. -L/mmc/lib -L/mmc/usr/lib hello.o -lgcc --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state --as-needed -lgcc_s --pop-state /mmc/lib/gcc/arm-tomatoware-linux-uclibcgnueabi/12.1.0/crtend.o /mmc/usr/lib/crtn.o Dwarf Error: wrong version in compilation unit header (is 5, should be 2, 3, or 4) [in module /mmc/lib/ld-uClibc.so.1] Can't read data for section '.debug_info' in file '/mmc/lib/libLLVM-14.so' Dwarf Error: wrong version in compilation unit header (is 5, should be 2, 3, or 4) [in module /mmc/usr/lib/libstdc++.so.6] Dwarf Error: wrong version in compilation unit header (is 5, should be 2, 3, or 4) [in module /mmc/lib/libgcc_s.so.1] Dwarf Error: wrong version in compilation unit header (is 5, should be 2, 3, or 4) [in module /mmc/lib/libc.so.0] Dwarf Error: wrong version in compilation unit header (is 5, should be 2, 3, or 4) [in module /mmc/lib/libffi.so.8] Dwarf Error: wrong version in compilation unit header (is 5, should be 2, 3, or 4) [in module /mmc/lib/libedit.so.0] Dwarf Error: wrong version in compilation unit header (is 5, should be 2, 3, or 4) [in module /mmc/lib/libxml2.so.2] Dwarf Error: wrong version in compilation unit header (is 5, should be 2, 3, or 4) [in module /mmc/lib/liblzma.so.5] [New LWP 27688] [New LWP 27689] Thread 2 "ld.lld" received signal SIGSEGV, Segmentation fault. [Switching to LWP 27688] 0x42deada0 in std::condition_variable::wait(std::unique_lock<std::mutex>&)@GLIBCXX_3.4.11 () from /mmc/usr/lib/libstdc++.so.6
next reply other threads:[~2022-05-25 17:32 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-25 17:32 lancethepants at gmail dot com [this message] 2022-05-26 9:18 ` [Bug libstdc++/105730] " marxin at gcc dot gnu.org 2022-05-26 9:18 ` marxin at gcc dot gnu.org 2022-10-25 7:17 ` [Bug libstdc++/105730] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-10-25 11:57 ` redi at gcc dot gnu.org 2022-10-25 12:01 ` redi at gcc dot gnu.org 2022-12-20 13:48 ` rguenth at gcc dot gnu.org 2022-12-20 15:50 ` pinskia at gcc dot gnu.org 2022-12-21 11:52 ` redi at gcc dot gnu.org 2022-12-21 12:10 ` redi at gcc dot gnu.org 2022-12-21 12:24 ` glex.spb at gmail dot com 2022-12-21 13:22 ` redi at gcc dot gnu.org 2022-12-21 13:22 ` redi at gcc dot gnu.org 2022-12-21 13:45 ` glex.spb at gmail dot com 2022-12-22 23:35 ` cvs-commit at gcc dot gnu.org 2023-01-17 18:25 ` [Bug libstdc++/105730] [12 " lancethepants at gmail dot com 2023-01-17 19:01 ` redi at gcc dot gnu.org 2023-01-17 19:23 ` glex.spb at gmail dot com 2023-01-18 15:14 ` cvs-commit at gcc dot gnu.org 2023-01-18 15:15 ` redi 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-105730-4@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).