public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "townsend at astro dot wisc.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/112828] Abort with malloc(): corrupted top size Date: Sun, 03 Dec 2023 16:54:00 +0000 [thread overview] Message-ID: <bug-112828-4-D40JRvrjwP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112828-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112828 --- Comment #4 from Rich Townsend <townsend at astro dot wisc.edu> --- Another data point for MacOS/Intel (10.13.6, High Sierra) -- with the character vars set to length 64, the crash is as follows: test(3287,0x7fff8fc11380) malloc: *** error for object 0x7fe44cc03b58: incorrect checksum for freed object - object was probably modified after being freed. *** set a breakpoint in malloc_error_break to debug Program received signal SIGABRT: Process abort signal. Backtrace for this error: #0 0x105c19a5e #1 0x105c18c1d #2 0x7fff57818f59 Abort trap: 6 Again, commenting out the allocate(..., STAT=stat) line makes the problem go away. Reducing the length to <=24 also resolves the problem.
next prev parent reply other threads:[~2023-12-03 16:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-02 23:12 [Bug fortran/112828] New: " townsend at astro dot wisc.edu 2023-12-03 13:38 ` [Bug fortran/112828] " fxcoudert at gcc dot gnu.org 2023-12-03 15:01 ` townsend at astro dot wisc.edu 2023-12-03 16:28 ` townsend at astro dot wisc.edu 2023-12-03 16:54 ` townsend at astro dot wisc.edu [this message] 2023-12-03 18:33 ` townsend at astro dot wisc.edu 2023-12-03 20:45 ` anlauf 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-112828-4-D40JRvrjwP@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).