public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at logicalclocks dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104244] New: Crash compiling RonDB 22.01 on Oracle Linux 8 on ARM Date: Wed, 26 Jan 2022 15:39:02 +0000 [thread overview] Message-ID: <bug-104244-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104244 Bug ID: 104244 Summary: Crash compiling RonDB 22.01 on Oracle Linux 8 on ARM Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mikael at logicalclocks dot com Target Milestone: --- Created attachment 52295 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52295&action=edit crash info Compiled RonDB 22.01.0 with this as last commit: commit 7da259292bedb03ca9860c8e4fa77af2e527af6f (HEAD -> 22.01, origin/22.01) Author: Mikael Ronstr<C3><B6>m <mikael.ronstrom@gmail.com> Date: Wed Jan 26 13:45:37 2022 +0100 ndb_binlog.ndb_binlog_index hangs in debug mode Found at github.com/mronstro/rondb in branch 22.01 Linux instance-20220126-1319 5.4.17-2102.204.4.4.el8uek.aarch64 #2 SMP Tue Aug 17 20:32:12 PDT 2021 aarch64 aarch64 aarch64 GNU/Linux [opc@instance-20220126-1319 err_build]$ /opt/rh/gcc-toolset-10/root/bin/gcc --version gcc (GCC) 10.3.1 20210422 (Red Hat 10.3.1-1.2.0.1) Copyright (C) 2020 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compilation command: git clone https://github.com/mronstro/rondb rondb_22010 git checkout 22.01 mkdir err_build cd err_build ../build_scripts/build_script_err.sh
next reply other threads:[~2022-01-26 15:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-26 15:39 mikael at logicalclocks dot com [this message] 2022-01-26 18:49 ` [Bug c++/104244] " pinskia at gcc dot gnu.org 2022-01-26 18:50 ` pinskia at gcc dot gnu.org 2022-01-26 22:34 ` mikael at logicalclocks dot com 2022-01-26 22:38 ` pinskia at gcc dot gnu.org 2022-01-26 22:39 ` pinskia at gcc dot gnu.org 2022-01-26 22:43 ` mikael at logicalclocks dot com 2022-01-26 22:52 ` mikael at logicalclocks dot com 2024-04-13 1:11 ` pinskia 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-104244-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).