public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/106915] New: ICE/segfault during parsing with modules and invalid code in malloc Date: Mon, 12 Sep 2022 17:35:02 +0000 [thread overview] Message-ID: <bug-106915-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106915 Bug ID: 106915 Summary: ICE/segfault during parsing with modules and invalid code in malloc Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- Created attachment 53564 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53564&action=edit Testcase the following code ICEs either in variant (A) with: corrupted size vs. prev_size ... 0x7f18078ba08f ??? /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0 0x7f180790ca63 malloc_consolidate /build/glibc-SzIz7B/glibc-2.31/malloc/malloc.c:4492 0x7f180790ec82 _int_malloc Or in Variant (B) with: Error: Expecting END MODULE statement at (1) malloc(): mismatching next->prev_size (unsorted) malloc(): mismatching next->prev_size (unsorted) gfortran: internal compiler error: Aborted signal terminated program f951 The second variant seems to work also without -fopenmp, even though it has 'USE omp_lib'.
next reply other threads:[~2022-09-12 17:35 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-12 17:35 burnus at gcc dot gnu.org [this message] 2022-09-12 19:46 ` [Bug fortran/106915] " marxin at gcc dot gnu.org 2022-09-12 19:46 ` marxin 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-106915-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).