From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13780 invoked by alias); 30 Oct 2011 20:09:33 -0000 Received: (qmail 13771 invoked by uid 22791); 30 Oct 2011 20:09:29 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 30 Oct 2011 20:09:16 +0000 From: "dm.vl.ivanov at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/50926] New: Output to 'fort.6" file instead of console Date: Sun, 30 Oct 2011 20:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: dm.vl.ivanov at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-10/txt/msg03160.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50926 Bug #: 50926 Summary: Output to 'fort.6" file instead of console Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: dm.vl.ivanov@gmail.com Console output suddenly stops to be console: at some point (usually when write(*,*) and write(6,*) operators are being used for some times but non only in that case, see the details below) the "fort.6" file is being created and fill with the rest of program's output. Seems not a very big deal but it is quite uncomfortable and eliminates the possibility to make a console-interactive program. I also tried to avoid using "write" and mix my fortran code with C module (compiled with g++) containing functions for console output. It helps just a bit: some more strings go to the console and some less - to the "fort.6" file. This seems to be exactly the matter of compiler, not anything else: the same code compiled with ifort runs just fine, no problems noticed. I imagine some more details would be good but my code is too big to upload here. I can just tell some numbers: about 10 times write(*,*) and write(6,*) functions produce their output to the console, all the rest - to the "fort.6" file. When I use C functions instead of fortran's "write" this number becomes slightly more, about 15 strings show up at the console. Environment: gcc version 4.6.1 (Debian 4.6.1-15), Debian testing/sid