public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108097] std::stacktrace AddressSanitizer: new-delete-type-mismatch on 0x615000000080 in thread T0
Date: Wed, 14 Dec 2022 14:18:54 +0000 [thread overview]
Message-ID: <bug-108097-4-9QUyI2TrCD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108097-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108097
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:e9d58614b0b8eebd64d568fa22cd31faaa5f8dce
commit r12-8985-ge9d58614b0b8eebd64d568fa22cd31faaa5f8dce
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Dec 14 11:58:05 2022 +0000
libstdc++: Fix size passed to operator delete [PR108097]
The number of elements gets stored in _M_capacity so use a separate
variable for the number of bytes to allocate.
libstdc++-v3/ChangeLog:
PR libstdc++/108097
* include/std/stacktrace (basic_stracktrace::_Impl): Do not
multiply N by sizeof(value_type) when allocating.
(cherry picked from commit 881c6cabce5d0b27285ed41bd6dabdf48848cce7)
next prev parent reply other threads:[~2022-12-14 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 11:39 [Bug libstdc++/108097] New: " unlvsur at live dot com
2022-12-14 11:39 ` [Bug libstdc++/108097] " unlvsur at live dot com
2022-12-14 11:46 ` unlvsur at live dot com
2022-12-14 11:46 ` redi at gcc dot gnu.org
2022-12-14 11:47 ` redi at gcc dot gnu.org
2022-12-14 11:48 ` unlvsur at live dot com
2022-12-14 11:49 ` unlvsur at live dot com
2022-12-14 11:52 ` redi at gcc dot gnu.org
2022-12-14 11:54 ` redi at gcc dot gnu.org
2022-12-14 11:56 ` redi at gcc dot gnu.org
2022-12-14 14:11 ` cvs-commit at gcc dot gnu.org
2022-12-14 14:12 ` redi at gcc dot gnu.org
2022-12-14 14:18 ` cvs-commit at gcc dot gnu.org [this message]
2022-12-14 14:19 ` 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-108097-4-9QUyI2TrCD@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).