public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108097] New: std::stacktrace AddressSanitizer: new-delete-type-mismatch on 0x615000000080 in thread T0 Date: Wed, 14 Dec 2022 11:39:01 +0000 [thread overview] Message-ID: <bug-108097-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108097 Bug ID: 108097 Summary: std::stacktrace AddressSanitizer: new-delete-type-mismatch on 0x615000000080 in thread T0 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- Created attachment 54089 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54089&action=edit stacktrace sanitizer stderr I try to crossback compiling stacktrace from windows to linux D:\hg\fast_io\.wunao>x86_64-pc-linux-gnu-g++ -o stacktrace stacktrace.cc -Ofast -std=c++23 -g -march=native -I../include -lstdc++_libbacktrace -fsanitize=address,undefined $ ./stacktrace 2>err.txt at D:\hg\fast_io\.wunao/stacktrace.cc:6 at :0 at :0 at :0
next reply other threads:[~2022-12-14 11:39 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-14 11:39 unlvsur at live dot com [this message] 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 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@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).