public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/110433] ASAN reports mismatching new/delete when compiling analyzer testcases
Date: Wed, 28 Jun 2023 09:41:35 +0000 [thread overview]
Message-ID: <bug-110433-4-RPdsZ1iZae@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110433-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110433
--- Comment #2 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Here is the promised longer trace (from compiling
testsuite/gcc.dg/analyzer/out-of-bounds-diagram-5-unicode.c):
=================================================================
==58010==ERROR: AddressSanitizer: new-delete-type-mismatch on 0x50d000000a00 in
thread T0:
object passed to delete has wrong type:
size of the allocated type: 136 bytes;
size of the deallocated type: 104 bytes.
#0 0x83eba8 in operator delete(void*, unsigned long)
/home/worker/buildworker/tiber-gcc-asan/build/libsanitizer/asan/asan_new_delete.cpp:164
#1 0x51e6e45 in
std::default_delete<ana::svalue_spatial_item>::operator()(ana::svalue_spatial_item*)
const
/home/worker/buildworker/tiber-gcc-asan/objdir/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/bits/unique_ptr.h:99
#2 0x51e6e45 in std::unique_ptr<ana::svalue_spatial_item,
std::default_delete<ana::svalue_spatial_item> >::~unique_ptr()
/home/worker/buildworker/tiber-gcc-asan/objdir/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/bits/unique_ptr.h:404
#3 0x51e6e45 in ana::access_diagram_impl::~access_diagram_impl()
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/access-diagram.cc:1728
#4 0x51e703c in ana::access_diagram_impl::~access_diagram_impl()
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/access-diagram.cc:1728
#5 0x4e97142 in
std::default_delete<text_art::widget>::operator()(text_art::widget*) const
/home/worker/buildworker/tiber-gcc-asan/objdir/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/bits/unique_ptr.h:99
#6 0x4e97142 in std::unique_ptr<text_art::widget,
std::default_delete<text_art::widget> >::~unique_ptr()
/home/worker/buildworker/tiber-gcc-asan/objdir/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/bits/unique_ptr.h:404
#7 0x4e97142 in text_art::wrapper_widget::~wrapper_widget()
/home/worker/buildworker/tiber-gcc-asan/build/gcc/text-art/widget.h:136
#8 0x4e97142 in ana::access_diagram::~access_diagram()
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/access-diagram.h:149
#9 0x4e97142 in
ana::out_of_bounds::make_access_diagram(ana::access_operation const&,
text_art::style_manager&, text_art::theme const&, ana::logger*) const
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/bounds-checking.cc:192
#10 0x4e97142 in ana::out_of_bounds::maybe_show_diagram(ana::logger*) const
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/bounds-checking.cc:169
#11 0x4e9928c in ana::out_of_bounds::maybe_show_notes(unsigned int,
ana::logger*) const
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/bounds-checking.cc:125
#12 0x4e9928c in ana::concrete_buffer_overflow::emit(rich_location*,
ana::logger*)
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/bounds-checking.cc:333
#13 0x4eee9ed in
ana::diagnostic_manager::emit_saved_diagnostic(ana::exploded_graph const&,
ana::saved_diagnostic const&)
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/diagnostic-manager.cc:1424
#14 0x4efca7a in ana::dedupe_winners::emit_best(ana::diagnostic_manager*,
ana::exploded_graph const&)
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/diagnostic-manager.cc:1311
#15 0x4eefd35 in
ana::diagnostic_manager::emit_saved_diagnostics(ana::exploded_graph const&)
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/diagnostic-manager.cc:1363
#16 0x2a647b6 in ana::impl_run_checkers(ana::logger*)
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/engine.cc:6139
#17 0x2a66f59 in ana::run_checkers()
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/engine.cc:6213
#18 0x2a2f8dc in execute
/home/worker/buildworker/tiber-gcc-asan/build/gcc/analyzer/analyzer-pass.cc:87
#19 0x197af8b in execute_one_pass(opt_pass*)
/home/worker/buildworker/tiber-gcc-asan/build/gcc/passes.cc:2651
#20 0x197d6d0 in execute_ipa_pass_list(opt_pass*)
/home/worker/buildworker/tiber-gcc-asan/build/gcc/passes.cc:3100
#21 0xd6f193 in ipa_passes
/home/worker/buildworker/tiber-gcc-asan/build/gcc/cgraphunit.cc:2268
#22 0xd6f193 in symbol_table::compile()
/home/worker/buildworker/tiber-gcc-asan/build/gcc/cgraphunit.cc:2331
#23 0xd6f193 in symbol_table::compile()
/home/worker/buildworker/tiber-gcc-asan/build/gcc/cgraphunit.cc:2309
#24 0xd76f09 in symbol_table::finalize_compilation_unit()
/home/worker/buildworker/tiber-gcc-asan/build/gcc/cgraphunit.cc:2583
#25 0x1d81ed8 in compile_file
/home/worker/buildworker/tiber-gcc-asan/build/gcc/toplev.cc:471
#26 0x77e8fb in do_compile
/home/worker/buildworker/tiber-gcc-asan/build/gcc/toplev.cc:2126
#27 0x77e8fb in toplev::main(int, char**)
/home/worker/buildworker/tiber-gcc-asan/build/gcc/toplev.cc:2282
#28 0x789813 in main
/home/worker/buildworker/tiber-gcc-asan/build/gcc/main.cc:39
next prev parent reply other threads:[~2023-06-28 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 9:56 [Bug analyzer/110433] New: " jamborm at gcc dot gnu.org
2023-06-27 20:25 ` [Bug analyzer/110433] " dmalcolm at gcc dot gnu.org
2023-06-28 9:41 ` jamborm at gcc dot gnu.org [this message]
2023-07-21 0:29 ` cvs-commit at gcc dot gnu.org
2023-07-21 0:36 ` dmalcolm at gcc dot gnu.org
2023-07-22 18:18 ` jamborm 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-110433-4-RPdsZ1iZae@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).