public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kapinos at itc dot rwth-aachen.de" <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 07:50:12 +0000	[thread overview]
Message-ID: <bug-56659-4-fVBpfS2iH7@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 #7 from kapinos at itc dot rwth-aachen.de ---
Sorry, for not adding the reproducer again. It is very K.I.S.S.:

- make (or reuse) an dir w/o read permissions
- use it as include dir at *any* Fortran source including empty ones.

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
.......




$ cat runme007.sh
mkdir -p foo/bar
chmod 000 foo
echo
"-------------------------------------------------------------------------"
gfortran -c  -I./foo/bar mini.F90
echo "------------------------------------------------------------------------"
gfortran -v

$ cat mini.F90
program mini
end







On 10/6/21 11:23 PM, burnus at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56659
> 
> --- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> ---
> (In reply to Paul from comment #5)
>> Just tried all versions of gfortran available up to 10.2.0: the very same
>> 'internal compiler error' is still reported using the initial reproducer.
> 
> Can you share the initial reproducer? The email link to gmane no longer works
> and what is written in the the original description and in the other email
> lacks the details. It only has:
> 
> Test case:
> * mkdir -p foo/bar
> * chmod 000 foo
> * gfortran -cpp some_file.F90
> 
> But that obviously does not use 'foo/bar' at all.
> 
> I have no idea what's in 'some_file.F90'; the most straight-forward input would
> be:
>    echo '#include "foo/bar/file.f90"' > some_file.F90
> but when I try this, GCC 7, 8, 9, 10 of Ubuntu and the current development
> version all show the same:
>    some_file.F90:2:2:
>    Fatal Error: foo/bar/file.f90: Permission denied
> 
> (The off-by-one line number issue is PR 100904.)
> 
> I assume that your file contains something different - but what? Can you
> enlighten me?
> 
>   * * *
> 
> A couple of fixes were done in the development branch (to be released as GCC 12
> around April), cf. PR 55534.
>

  parent reply	other threads:[~2021-10-07  7:50 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 [this message]
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

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-fVBpfS2iH7@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).