public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/108109] [ICE] gfortran compilation fails calling 'free()' with 'malloc(): mismatching next->prev_size (unsorted)' Date: Wed, 14 Dec 2022 21:10:14 +0000 [thread overview] Message-ID: <bug-108109-4-zqijAkbY75@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108109-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108109 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2022-12-14 Status|UNCONFIRMED |NEW --- Comment #3 from anlauf at gcc dot gnu.org --- On my system I don't see glibc complaining, independent of MALLOC_PERTURB_=, however, with valgrind I do get an invalid read slightly deeper down, in ==21865== Invalid read of size 8 ==21865== at 0x95AD7D: add_dt_to_dt_list (resolve.cc:14470) ==21865== by 0x95AD7D: add_dt_to_dt_list (resolve.cc:14464) ==21865== by 0x95AD7D: resolve_fl_derived0(gfc_symbol*) [clone .part.0] (resolve.cc:15152) (Note the line numbers may slightly differ from yours.) So confirmed.
prev parent reply other threads:[~2022-12-14 21:10 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-14 18:37 [Bug fortran/108109] New: " burnus at gcc dot gnu.org 2022-12-14 19:34 ` [Bug fortran/108109] " anlauf at gcc dot gnu.org 2022-12-14 20:51 ` burnus at gcc dot gnu.org 2022-12-14 21:10 ` anlauf at gcc dot gnu.org [this message]
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-108109-4-zqijAkbY75@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).