public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi 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 11:52:12 +0000	[thread overview]
Message-ID: <bug-108097-4-VnCXtIp1d1@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 #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to cqwrteur from comment #5)
> Still crashing by replacing with std::cout

Yes, of course, which is why you should have used that in the first place. Your
own fast_io.h is irrelevant to the problem.

(In reply to cqwrteur from comment #6)
> std::cout and stdio bloat my binary.

Yes, I know, you never stop going on about it. You don't need to optimize the
binary size of reproducers posted in bugzilla though, do you? The point should
be to demonstrate the problem effectively, not minimise binary size.

Nobody is going to download your fast_io.h to reproduce a bug.

  parent reply	other threads:[~2022-12-14 11:52 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 [this message]
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
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-VnCXtIp1d1@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).