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] New: Segfault due to missing libcpp error handler for "gfortran -cpp" Date: Wed, 20 Mar 2013 07:29:00 -0000 [thread overview] Message-ID: <bug-56659-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56659 Bug #: 56659 Summary: Segfault due to missing libcpp error handler for "gfortran -cpp" Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org CC: kapinos@rz.rwth-aachen.de Reported by Paul Kapinos at fortran@gcc, http://thread.gmane.org/gmane.comp.gcc.fortran/40495 http://gcc.gnu.org/ml/fortran/2013-03/msg00083.html The problem is that libcpp calls an error handler, which is not set in f951. Namely, pfile->cb.error == NULL but should be point to a function; it has the the prototype: bool (*)(cpp_reader *, int, int, source_location, unsigned int, const char *, va_list *) C/C++ use: in c-opts.c: "cb->error = c_cpp_error;" the function is declared in c-family/c-common.c. Test case: * mkdir -p foo/bar * chmod 000 foo * gfortran -cpp some_file.F90
next reply other threads:[~2013-03-20 7:29 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-20 7:29 burnus at gcc dot gnu.org [this message] 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
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@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).