About 'error stop' statement

[Janne Blomqvist]

On Mon, Aug 7, 2017 at 9:59 AM, Angelo Graziosi
<angelo.graziosi@alice.it> wrote:
> Sorry if I insist on this,
>
> Il 07/08/2017 02:06, Damian Rouson ha scritto:
>>
>> for Linux, I’m guessing you used the OpenCoarrays windows-install.sh
>> installs
>
>
>
> Anton Shterenlikht wrote:
>>
>> If calling MPI_abort is deemed by the implementors
>> to be the quickest way, then this is acceptable.
>> If an image has initiated error termination
>
>
>
> but why do you thing I am using coarrays? I never used that and know almost
> nothing about that. The foo.f90 example, I cited, really use coarrays?
>
> I knew about 'error stop' reading code on the WEB and that DID NOT use
> coarrays at all (simple rewrite of old code). So all this is very confusing,
> now..
>
> Hmm... sure there isn't a bug somewhere?
>

I think the discussion of co-arrays here is entirely irrelevant.
You're not using co-arrays, and no co-array library should be linked
into your binary. What I think you're seeing is

a) In GCC 6, there is some bug in libbacktrace (the library GFortran
uses to print backtraces) on Windows, causing a segfault. This seems
to have been fixed in GCC 7. (I'm blaming libbacktrace here, because
the GFortran ERROR STOP implementation has not changed between 6 and
7. Though it could be some other change in the GCC Windows target
support as well, I guess.)

b) As of GCC 6, it was decided that ERROR STOP should print a
backtrace (IIRC it was discussed on this list, maybe you can dig it up
if you're curious..), which is why you're not seeing it when compiling
with GFortran 5.

-- 
Janne Blomqvist