public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gnu.iodaj at simplelogin dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108556] New: std::sort changes objects' member values
Date: Thu, 26 Jan 2023 10:05:13 +0000	[thread overview]
Message-ID: <bug-108556-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108556

            Bug ID: 108556
           Summary: std::sort changes objects' member values
           Product: gcc
           Version: 11.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gnu.iodaj at simplelogin dot com
  Target Milestone: ---

When working on a project, I tried using std::sort to sort a vector of objects,
and it resulted in a crash. After looking closer, valgrind reports lots of
invalid writes and the data is effectively modified during the sort.

This issue doesn't happen with stable_sort nor with small enough vectors.

The g++ versions tested are 11.3.0 and 12.1.0.

The system is a Dell Precision 5570 running Linux Mint 21.

g++ command is g++ -Wall -Wextra sort-bug.cpp (file in attachment)

The compiler output is none (no warnings, no errors, no line displayed)

Please find the attached file that serves as a minimal working example of this
bug.

Thank you.

             reply	other threads:[~2023-01-26 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 10:05 gnu.iodaj at simplelogin dot com [this message]
2023-01-26 10:06 ` [Bug libstdc++/108556] " gnu.iodaj at simplelogin dot com
2023-01-26 10:20 ` redi at gcc dot gnu.org
2023-01-26 10:23 ` redi at gcc dot gnu.org
2023-07-14 19:04 ` 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-108556-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).