Buffer overflow issues with NAGware f95 v 4.1
From: Madhusudan Singh (spammers-go-here_at_spam.invalid)
Date: 09/28/04
- Previous message: TimC: "Re: Avoiding compilation cascades"
- Next in thread: Gerry Thomas: "Re: Buffer overflow issues with NAGware f95 v 4.1"
- Reply: Gerry Thomas: "Re: Buffer overflow issues with NAGware f95 v 4.1"
- Reply: Jan Vorbrüggen: "Re: Buffer overflow issues with NAGware f95 v 4.1"
- Reply: Richard E Maine: "Re: Buffer overflow issues with NAGware f95 v 4.1"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 27 Sep 2004 20:39:58 -0400
Hi
Thanks to everyone who helped with the precision problem. It seems that the
maximum precision is selected_real_kind(15). It compiles now.
Anyways, I tried to run this program for whatever it was worth, and came up
against after a successful start :
Buffer overflow on output
Program terminated by fatal I/O error
Aborted
A google search for this yields :
http://www.nag.co.uk/nagware/NP/doc/faq.asp#FAQQ8
Now, from a practical standpoint, I have plenty of write statements in my
program and it would be painful to added the recl= clauses for each one of
them (btw. what is the debugger that comes with NAGware ?) just because NAG
is unable to deal with some formatted writes (never had such problems with
IFC or Sun f95). Is there some kind of global directive I could use to get
past this mess ?
Thanks.
(never knew working with NAG would be so painful)
- Previous message: TimC: "Re: Avoiding compilation cascades"
- Next in thread: Gerry Thomas: "Re: Buffer overflow issues with NAGware f95 v 4.1"
- Reply: Gerry Thomas: "Re: Buffer overflow issues with NAGware f95 v 4.1"
- Reply: Jan Vorbrüggen: "Re: Buffer overflow issues with NAGware f95 v 4.1"
- Reply: Richard E Maine: "Re: Buffer overflow issues with NAGware f95 v 4.1"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]