public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aluaces at udc dot es" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/110644] Error in gfc_format_decoder
Date: Wed, 18 Oct 2023 15:56:32 +0000 [thread overview]
Message-ID: <bug-110644-4-LS5BFEk53J@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110644-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
Alberto Luaces <aluaces at udc dot es> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aluaces at udc dot es
--- Comment #4 from Alberto Luaces <aluaces at udc dot es> ---
I got the same error in almost the same circumstances (crash in error.cc:1078).
I have a large codebase and I could not prepare a minimal testcase, but I have
built gfortran 13 from source with the aim to debug the crash.
Hoewever, even I set "set follow-fork-mode children", f951 crashes and I cannot
navigate through the backtrace nor see the arguments of the functions.
Is there any reference for debugging gcc in order to send some useful
information to this bug?
next prev parent reply other threads:[~2023-10-18 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 16:04 [Bug fortran/110644] New: " kyle.shores44 at gmail dot com
2023-07-12 17:46 ` [Bug fortran/110644] " kargl at gcc dot gnu.org
2023-10-13 19:41 ` jvdelisle at gcc dot gnu.org
2023-10-16 14:32 ` kyle.shores44 at gmail dot com
2023-10-18 15:56 ` aluaces at udc dot es [this message]
2023-10-18 17:03 ` sgk at troutmask dot apl.washington.edu
2023-10-19 8:00 ` aluaces at udc dot es
2023-10-19 15:44 ` sgk at troutmask dot apl.washington.edu
2023-10-19 16:00 ` aluaces at udc dot es
2023-10-19 16:19 ` sgk at troutmask dot apl.washington.edu
2023-10-20 15:13 ` aluaces at udc dot es
2023-10-20 17:29 ` sgk at troutmask dot apl.washington.edu
2023-10-23 15:16 ` aluaces at udc dot es
2024-03-06 3:40 ` jvdelisle at gcc dot gnu.org
2024-03-08 16:44 ` kyle.shores44 at gmail dot com
2024-03-08 16:56 ` kyle.shores44 at gmail dot com
2024-03-08 17:22 ` sgk at troutmask dot apl.washington.edu
2024-03-08 17:42 ` kyle.shores44 at gmail dot com
2024-03-08 17:42 ` kyle.shores44 at gmail dot com
2024-03-08 19:44 ` sgk at troutmask dot apl.washington.edu
2024-03-08 20:01 ` kyle.shores44 at gmail dot com
2024-03-08 20:32 ` sgk at troutmask dot apl.washington.edu
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-110644-4-LS5BFEk53J@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).