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.
