public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amy at amyspark dot me" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109806] New: 13.1.0 cc1plus stack smashing crash with C array of complex structs Date: Thu, 11 May 2023 02:26:03 +0000 [thread overview] Message-ID: <bug-109806-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806 Bug ID: 109806 Summary: 13.1.0 cc1plus stack smashing crash with C array of complex structs Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: amy at amyspark dot me Target Milestone: --- Hi, Coming from https://github.com/msys2/MINGW-packages/pull/16968#issuecomment-1541465457. I've found a crash in cc1plus 13.1.0 when building an array of ~68 structs in C++. The crash yields no report or crash handling, it just causes g++ to return exit code 1. However, I was able to trap the cc1plus execution line, and then run it manually under GDB. This yielded a symbolicated stacktrace that I've uploaded along with the preprocessed file (it's 1.6MB, so it was impossible to attach them here uncompressed): https://gist.github.com/amyspark/be93638fc5b5779594dd138aa8995860 GCC version data: Using built-in specs. COLLECT_GCC=D:\msys64\ucrt64\bin\gcc.exe COLLECT_LTO_WRAPPER=D:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.1.0/lto-wrapper.exe Target: x86_64-w64-mingw32 Configured with: ../gcc-13.1.0/configure --prefix=/ucrt64 --with-local-prefix=/ucrt64/local --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --with-native-system-header-dir=/ucrt64/include --libexecdir=/ucrt64/lib --enable-bootstrap --enable-checking=release --with-arch=nocona --with-tune=generic --enable-languages=c,lto,c++,fortran,ada,objc,obj-c++,jit --enable-shared --enable-static --enable-libatomic --enable-threads=posix --enable-graphite --enable-fully-dynamic-string --enable-libstdcxx-filesystem-ts --enable-libstdcxx-time --disable-libstdcxx-pch --enable-lto --enable-libgomp --disable-libssp --disable-multilib --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --with-libiconv --with-system-zlib --with-gmp=/ucrt64 --with-mpfr=/ucrt64 --with-mpc=/ucrt64 --with-isl=/ucrt64 --with-pkgversion=Rev4, Built by MSYS2 project --with-bugurl=https://github.com/msys2/MINGW-packages/issues --with-gnu-as --with-gnu-ld --enable-libstdcxx-debug --with-boot-ldflags="-static-libstdc++" --with-stage1-ldflags="-static-libstdc++" Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 13.1.0 (Rev4, Built by MSYS2 project) Prior to https://github.com/msys2/MINGW-packages/pull/17094, the CFLAGS value was (I added debug !strip to the PKGBUILD options to get debugging symbols): -g -march=nocona -msahf -mtune=generic -O2 -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector-strong -ggdb -Og -ffile-prefix-map=/c/Users/Amalia/Desktop/MINGW-packages/mingw-w64-gcc/src=/usr/src/debug/mingw-w64-gcc
next reply other threads:[~2023-05-11 2:26 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 2:26 amy at amyspark dot me [this message] 2023-05-11 2:48 ` [Bug tree-optimization/109806] " pinskia at gcc dot gnu.org 2023-05-11 6:46 ` rguenth at gcc dot gnu.org 2023-05-11 9:47 ` amy at amyspark dot me 2023-05-11 9:49 ` amy at amyspark dot me 2023-05-11 12:51 ` rguenth at gcc dot gnu.org 2023-05-11 18:01 ` pinskia at gcc dot gnu.org 2023-05-11 18:56 ` [Bug tree-optimization/109806] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-05-11 20:05 ` jakub at gcc dot gnu.org 2023-05-11 20:44 ` amy at amyspark dot me 2023-05-11 22:45 ` reiter.christoph at gmail dot com 2023-05-12 1:43 ` sjames at gcc dot gnu.org 2023-05-15 21:35 ` sjames at gcc dot gnu.org 2023-05-15 22:27 ` amonakov at gcc dot gnu.org 2023-05-15 22:35 ` sjames at gcc dot gnu.org 2023-05-15 22:41 ` jakub at gcc dot gnu.org 2023-05-15 22:49 ` sjames at gcc dot gnu.org 2023-07-27 9:26 ` rguenth at gcc dot gnu.org 2024-01-12 11:30 ` rguenth at gcc dot gnu.org 2024-01-12 21:12 ` amy at amyspark dot me 2024-01-13 2:23 ` amy at amyspark dot me
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-109806-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).