From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-432938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 12762 invoked by alias); 29 Oct 2013 20:21:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 12708 invoked by uid 55); 29 Oct 2013 20:21:50 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58913] Segmentation fault on real128 array
Date: Tue, 29 Oct 2013 20:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58913-4-4J9OLsunrz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58913-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58913-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-10/txt/msg02082.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913

--- Comment #6 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Oct 29, 2013 at 08:02:08PM +0000, rrodrigues at poli dot ufrj.br wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913
> 
> --- Comment #5 from Rodrigo Rodrigues <rrodrigues at poli dot ufrj.br> ---
> There is no compile error. Adding -g for running doesn't show any new
> information, just the same:
> 
> Program received signal SIGSEGV: Segmentation Fault
> - invalid memory reference.
> 
> Backtrace for this error:
> #0 ffffffff

You need to run the file within gdb to get a backtrace.
I don't use MingW so I'm not sure how to do this.  On
FreeBSD, one would do

% gfortran -o z a.f90
% gdb ./z
gdb> run
(segfault occurs)
gdb> bt
(trace of function calls)

> The dump file have:

A quick glance shows that the dump looks like what I have here.

> MAIN__ ()
> {

(snip)

>         _gfortran_transfer_array_write (&dt_parm.1, &parm.2, 16, 0);

What I hope gdb shows is that segfault occurs in this function.
This would then mean we have an OS specific issue.