public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nvwarr at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libf2c/11918] isatty does not call f_init
Date: Wed, 10 Sep 2003 06:22:00 -0000	[thread overview]
Message-ID: <20030910062210.16079.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030814122008.11918.nvwarr@hotmail.com>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11918



------- Additional Comments From nvwarr at hotmail dot com  2003-09-10 06:22 -------
I originally reported this but to RedHat's bugzilla with a test case. It seems
that subject line was forwarded by someone but without the explanation. So I'm
cutting and pasting what I sent to RedHat...


Description of problem:
Using a main program in C and a subroutine in Fortran, where the Fortran
uses isatty without using any other Fortran I/O, results in a segmentation fault
at that point.

Inserting another Fortran I/O operation before the call to isatty works around
the problem. Alternatively, calling f_init explicitly from the C code before
calling the Fortran also works.

My problem occurs in a large complicated set of code mixing C and Fortran, but
the example below illustrates the problem.

Version-Release number of selected component (if applicable):
gcc-g77-3.2-7


  parent reply	other threads:[~2003-09-10  6:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14 12:20 [Bug libf2c/11918] New: " nvwarr at hotmail dot com
2003-08-23  2:54 ` [Bug libf2c/11918] " pinskia at gcc dot gnu dot org
2003-08-24 22:59 ` dhazeghi at yahoo dot com
2003-09-10  6:22 ` nvwarr at hotmail dot com [this message]
2003-09-13 21:39 ` pinskia at gcc dot gnu dot org
2003-09-13 22:16 ` pinskia at gcc dot gnu dot org
2003-09-21 18:48 ` pinskia at gcc dot gnu dot org
2003-12-09 18:17 ` dhazeghi at yahoo dot com

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=20030910062210.16079.qmail@sources.redhat.com \
    --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).