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/56659] Segfault due to missing libcpp error handler for "gfortran -cpp" Date: Fri, 08 Oct 2021 07:58:58 +0000 [thread overview] Message-ID: <bug-56659-4-3wDQxrfbl7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56659-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56659 --- Comment #10 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to Manuel López-Ibáñez from comment #9) > (In reply to Tobias Burnus from comment #8) > > f951: Warning: Include directory ‘foo/bar/’: Permission denied > > <built-in>: Error: foo/bar: Permission denied > > (The <built-in> > > Are you sure the Error is produced *after* entering the file (by entering I > mean pushing the file into the include stack and thus updating the > line-map). I was too brief. It occurs between the two. The full version is: If everything is not on the file stack 'f951' is printed, then the '<build-in>' stuff happens, from "gfc_cpp_init": cpp_change_file (cpp_in, LC_RENAME, _("<built-in>")); .... cpp_change_file (cpp_in, LC_RENAME, _("<command-line>")); (similar: c-family/c-opts.c: c_finish_options) This could be undone (to print 'f951') by calling cpp_change_file with to_file = NULL – but I am sure it won't have undesired side effect. And only after the file has been successfully opened, linemap_add is called. Thus, the '<built-in>' shows up between gfc_cpp_init() and linemap_add. Or code wise, in gfc_init: if (!gfc_cpp_enabled ()) { linemap_add (line_table, LC_ENTER, false, gfc_source_file, 1); linemap_add (line_table, LC_RENAME, false, "<built-in>", 0); } else gfc_cpp_init_0 (); ... if (gfc_cpp_enabled ()) gfc_cpp_init (); ... gfc_new_file (); with gfc_new_file: if (gfc_cpp_enabled ()) { gfc_cpp_preprocess (gfc_source_file); if (!gfc_cpp_preprocess_only ()) load_file (gfc_cpp_temporary_file (), gfc_source_file, true); } else load_file (gfc_source_file, NULL, true); and in load_file: input = gfc_open_file (realfilename); if (input == NULL) gfc_fatal_error ("Cannot open file %qs", filename); ... f = get_file (filename, (initial && !preprocessed_p) ? LC_RENAME : LC_ENTER); the latter then calls linemap_add (line_table, reason, false, f->filename, 1); > In either case, this points to some mess in the line-map stack. Suggestions how to improve the code above?
prev parent reply other threads:[~2021-10-08 7:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-20 7:29 [Bug fortran/56659] New: " burnus at gcc dot gnu.org 2013-03-20 10:49 ` [Bug fortran/56659] " rguenth at gcc dot gnu.org 2021-09-24 7:54 ` burnus at gcc dot gnu.org 2021-10-06 11:22 ` kapinos at rz dot rwth-aachen.de 2021-10-06 21:23 ` burnus at gcc dot gnu.org 2021-10-07 7:50 ` kapinos at itc dot rwth-aachen.de 2021-10-07 10:44 ` burnus at gcc dot gnu.org 2021-10-08 7:09 ` manu at gcc dot gnu.org 2021-10-08 7:58 ` burnus 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-56659-4-3wDQxrfbl7@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).