public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "knoepfel at fnal dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111685] New: Segfault while sorting on array element address
Date: Tue, 03 Oct 2023 18:57:40 +0000 [thread overview]
Message-ID: <bug-111685-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111685
Bug ID: 111685
Summary: Segfault while sorting on array element address
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: knoepfel at fnal dot gov
Target Milestone: ---
The following file (`sort-bug.cpp`) results in a segmentation violation:
```
#include <algorithm>
#include <array>
#include <cassert>
#include <vector>
int main()
{
std::vector vnums{1, 5, 4};
std::array anums{1, 5, 4};
int nums[] = {1, 5, 4};
auto cmp = [](auto&& a, auto&& b) { return &a < &b; };
std::sort(vnums.begin(), vnums.end(), cmp);
std::sort(anums.begin(), anums.end(), cmp); // segfault
std::sort(nums, nums + 3, cmp); // segfault
}
```
*Expected result*: the `vnums`, `anums`, and `nums` variables remain unaltered
after the invocation to `std::sort`.
*Compiler info*:
- Target: x86_64-pc-linux-gnu
- Configured with:
/scratch/workspace/art-build-base/v13_02_00-e28/SLF7/build/gcc/v13_1_0/src/gcc-13.1.0/configure
--enable-__cxa_atexit --enable-checking=release
--enable-compressed-debug-sections=all
--enable-languages=c,c++,fortran,go,objc,obj-c++ --enable-libstdcxx-time=rt
--enable-plugin --enable-stage1-checking=all --enable-threads=posix
--prefix=/scratch/workspace/art-build-base/v13_02_00-e28/SLF7/build/gcc/v13_1_0/Linux64bit+3.10-2.17
--with-system-zlib --enable-lto --with-zstd --enable-link-serialization=15
- Thread model: posix
- Supported LTO compression algorithms: zlib zstd
- gcc version 13.1.0 (GCC)
*Compiler/runtime command*: `g++ sort-bug.cpp -o sort-bug -std=c++20 -pedantic
-Werror -Wall; ./sort-bug`
next reply other threads:[~2023-10-03 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 18:57 knoepfel at fnal dot gov [this message]
2023-10-03 19:06 ` [Bug libstdc++/111685] " pinskia at gcc dot gnu.org
2023-10-03 19:10 ` pinskia at gcc dot gnu.org
2023-10-03 19:14 ` knoepfel at fnal dot gov
2023-10-03 19:19 ` knoepfel at fnal dot gov
2023-10-03 21:24 ` pinskia at gcc dot gnu.org
2023-10-03 21:37 ` pinskia at gcc dot gnu.org
2023-10-04 1:35 ` xry111 at gcc dot gnu.org
2023-10-04 9:48 ` redi at gcc dot gnu.org
2023-10-04 10:06 ` redi at gcc dot gnu.org
2023-10-04 17:46 ` fchelnokov at gmail dot com
2023-10-05 19:27 ` knoepfel at fnal dot gov
2023-10-06 10:10 ` fchelnokov at gmail dot com
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-111685-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: link
Be 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).