Re: forrtl: severe (174): SIGSEGV due to output file.

On Tue, 5 Aug 2008 06:34:32 -0700 (PDT), habzone2007@xxxxxxxxx wrote:

***************************************
fortcom: Error: mercury6_2.for, line 5607: Character length argument
mismatch. [' ']
% ' ',1,'files.in',8)
--------^

This indicates that you are passing a short character argument to a routine
which declares the corresponding dummy argument as larger (for example here,
CHARACTER(10).) This can cause reading or writing data outside the value and
can create serious problems. You should be using CHARACTER(*) for the dummy
arguments in general.

fortcom: Error: mercury6_2.for, line 231: Declaration of routine
'MFO_USER' conflicts with a previous declaration
subroutine mfo_user (time,jcen,nbod,nbig,m,x,v,a)

This might be a compiler bug triggered by the use of generated interface
checking. I know we have fixed similar problems in the past. I'd need to see
the example source to know for sure. I suggest ignoring it for now.

--
Steve Lionel
Developer Products Division
Intel Corporation
Nashua, NH

For email address, replace "invalid" with "com"

User communities for Intel Software Development Products
http://softwareforums.intel.com/
Intel Fortran Support
http://support.intel.com/support/performancetools/fortran
My Fortran blog
http://www.intel.com/software/drfortran
.

Relevant Pages

  • Re: Q: ENTRY Argument List
    ... > character) text string, the text string data would not be passed ... "If a scalar dummy argument is of type default character, ... tricky things to look out for where ENTRY is involved, ...
    (comp.lang.fortran)
  • Re: Intel fortran and fortran 77 standard!
    ... > | value dummy argument use CHARACTER(*) instead. ... Intel compiler settings: ...
    (comp.lang.fortran)
  • Re: forrtl: severe (174): SIGSEGV due to output file.
    ... This indicates that you are passing a short character argument to a routine ... this is the problem causing the symptoms mentioned, ... Most cases of using character lengths other than * for dummy ... the exceptions are awfully rare. ...
    (comp.lang.fortran)
  • Re: Intel fortran and fortran 77 standard!
    ... value dummy argument use CHARACTER(*) instead. ... other code work work also, ...
    (comp.lang.fortran)
  • Re: How can I simply use (old) routines?
    ... Dummy arguments are declared in the argument list. ... no IMPLICIT NONE, they are declared at first use). ... argument list declares only one specific attribute of them - they they ... Although, if I'm trying to make a fine point, it's probably not a good idea to use vague language, is it? ...
    (comp.lang.fortran)