<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic f90 compilation core dumps on an array constructor statement in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/f90-compilation-core-dumps-on-an-array-constructor-statement/m-p/3950603#M97787</link>
    <description>-- f90 core dumps on the following code:&lt;BR /&gt;program test&lt;BR /&gt;! character(len=5) ::  a_list(2) = (/ '12345','1234' /)&lt;BR /&gt;  character(len=5) ::  a_list(2) = (/ '1234','12345' /)&lt;BR /&gt;end do&lt;BR /&gt;&lt;BR /&gt;] f90 +source=free  03.f&lt;BR /&gt;03.f&lt;BR /&gt;   program TEST&lt;BR /&gt;&lt;BR /&gt;** Floating Point Exception **&lt;BR /&gt;( 0)  0x002481a0   coredump + 0x10  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 1)  0x001f809c   cry_and_die + 0x3c  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 2)  0x001f8738   f_onsignal + 0x30  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 3)  0x002d95ac   compsignal + 0x1c  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 4)  0x009d4d98   _sigreturn  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 5)  0x00246840   blockcopy + 0x28  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 6)  0x0028305c   arrayconaction1 + 0xfcc  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 7)  0x00287b04   evalinitexpr + 0x290  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 8)  0x001c9764   generatetriads + 0xfc64  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 9)  0x001a8e2c   processprogramblock + 0x64  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(10)  0x001b6dd4   visitpreorder + 0x58  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(11)  0x001b6e80   visitprogramblocklist + 0x20  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(12)  0x001cf528   seman2 + 0x144  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(13)  0x0021f17c   fort90 + 0x1bd14  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(14)  0x001ae378   main + 0x18  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(15)  0x009864d8   _start + 0x80  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(16)  0x001a82a0   $START$ + 0x1a0  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;f90: error 71: Signal 6 (abort) while compiling 03.f&lt;BR /&gt;&lt;BR /&gt;-- The fix appears to be having the first string element in the array constructor match the "len" of the declaration. For instance:&lt;BR /&gt;character(len=5) ::  a_list(2) = (/ '12345','1234' /)&lt;BR /&gt;&lt;BR /&gt;Question1: When using an array constructor on an array of strings should each elements character length match exactly the declared length? &lt;BR /&gt;&lt;BR /&gt;Question2: Is the workaround (of having the first alement in the array constructor exactly match the declaration length, but elements that follow can have any length not to exceed the delclared max character length) going to cause some memory nastiness in the executable?&lt;BR /&gt;&lt;BR /&gt;--some system information&lt;BR /&gt;hpux pa-risc&lt;BR /&gt;] what /opt/fortran90/bin/f90&lt;BR /&gt;/opt/fortran90/bin/f90:&lt;BR /&gt;        HP-UX f90 B3907DB/B3909DB B.11.11.99.02 PHSS_34398 / B.11.23.33 PHSS_34399 (PA RISC) Tue Oct 31 09:12:32 CST 2006&lt;BR /&gt;        HP F90 v3.1.2&lt;BR /&gt;         $ PATCH/11.00:PHCO_95167  Oct  1 1998 13:46:32 $ &lt;BR /&gt;</description>
    <pubDate>Fri, 23 Feb 2007 16:44:18 GMT</pubDate>
    <dc:creator>phillip stout</dc:creator>
    <dc:date>2007-02-23T16:44:18Z</dc:date>
    <item>
      <title>f90 compilation core dumps on an array constructor statement</title>
      <link>https://community.hpe.com/t5/operating-system-linux/f90-compilation-core-dumps-on-an-array-constructor-statement/m-p/3950603#M97787</link>
      <description>-- f90 core dumps on the following code:&lt;BR /&gt;program test&lt;BR /&gt;! character(len=5) ::  a_list(2) = (/ '12345','1234' /)&lt;BR /&gt;  character(len=5) ::  a_list(2) = (/ '1234','12345' /)&lt;BR /&gt;end do&lt;BR /&gt;&lt;BR /&gt;] f90 +source=free  03.f&lt;BR /&gt;03.f&lt;BR /&gt;   program TEST&lt;BR /&gt;&lt;BR /&gt;** Floating Point Exception **&lt;BR /&gt;( 0)  0x002481a0   coredump + 0x10  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 1)  0x001f809c   cry_and_die + 0x3c  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 2)  0x001f8738   f_onsignal + 0x30  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 3)  0x002d95ac   compsignal + 0x1c  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 4)  0x009d4d98   _sigreturn  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 5)  0x00246840   blockcopy + 0x28  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 6)  0x0028305c   arrayconaction1 + 0xfcc  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 7)  0x00287b04   evalinitexpr + 0x290  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 8)  0x001c9764   generatetriads + 0xfc64  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;( 9)  0x001a8e2c   processprogramblock + 0x64  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(10)  0x001b6dd4   visitpreorder + 0x58  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(11)  0x001b6e80   visitprogramblocklist + 0x20  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(12)  0x001cf528   seman2 + 0x144  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(13)  0x0021f17c   fort90 + 0x1bd14  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(14)  0x001ae378   main + 0x18  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(15)  0x009864d8   _start + 0x80  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;(16)  0x001a82a0   $START$ + 0x1a0  [/opt/fortran90/lbin/f90com32]&lt;BR /&gt;f90: error 71: Signal 6 (abort) while compiling 03.f&lt;BR /&gt;&lt;BR /&gt;-- The fix appears to be having the first string element in the array constructor match the "len" of the declaration. For instance:&lt;BR /&gt;character(len=5) ::  a_list(2) = (/ '12345','1234' /)&lt;BR /&gt;&lt;BR /&gt;Question1: When using an array constructor on an array of strings should each elements character length match exactly the declared length? &lt;BR /&gt;&lt;BR /&gt;Question2: Is the workaround (of having the first alement in the array constructor exactly match the declaration length, but elements that follow can have any length not to exceed the delclared max character length) going to cause some memory nastiness in the executable?&lt;BR /&gt;&lt;BR /&gt;--some system information&lt;BR /&gt;hpux pa-risc&lt;BR /&gt;] what /opt/fortran90/bin/f90&lt;BR /&gt;/opt/fortran90/bin/f90:&lt;BR /&gt;        HP-UX f90 B3907DB/B3909DB B.11.11.99.02 PHSS_34398 / B.11.23.33 PHSS_34399 (PA RISC) Tue Oct 31 09:12:32 CST 2006&lt;BR /&gt;        HP F90 v3.1.2&lt;BR /&gt;         $ PATCH/11.00:PHCO_95167  Oct  1 1998 13:46:32 $ &lt;BR /&gt;</description>
      <pubDate>Fri, 23 Feb 2007 16:44:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/f90-compilation-core-dumps-on-an-array-constructor-statement/m-p/3950603#M97787</guid>
      <dc:creator>phillip stout</dc:creator>
      <dc:date>2007-02-23T16:44:18Z</dc:date>
    </item>
  </channel>
</rss>

