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: Thu, 07 Oct 2021 10:44:45 +0000	[thread overview]
Message-ID: <bug-56659-4-aXt6jeByXy@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 #8 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to kapinos from comment #7)
> The output of gfortran 10.2.0 was added previously, cf.
>  > f951: Warning: Include directory ‘./foo/bar’: Permission denied
>  > f951: internal compiler error: in cpp_diagnostic_at, at libcpp/errors.c:41

I can reproduce this with GCC 7 to 10. But with my patch for PR 100904 (see
commit there), this is fixed in GCC 12:

  f951: Warning: Include directory ‘foo/bar/’: Permission denied
  <built-in>: Error: foo/bar: Permission denied

(The <built-in> shows up when entering a file but the file is not yet there.
Not ideal,
but not that quick to fix. Once the file is read, that's replaced by the file
name and line number. Still, the <built-in> issue should be fixed eventually.)

  parent reply	other threads:[~2021-10-07 10:44 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 [this message]
2021-10-08  7:09 ` manu at gcc dot gnu.org
2021-10-08  7:58 ` burnus 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-56659-4-aXt6jeByXy@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).