From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 63176 invoked by alias); 15 Apr 2015 00:19:16 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 63155 invoked by uid 48); 15 Apr 2015 00:19:12 -0000 From: "giorgianb at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/65766] New: gFortran Compiler SEGFAULTING on compiling simple program Date: Wed, 15 Apr 2015 00:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.9.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: giorgianb at gmail dot com 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: 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: 2015-04/txt/msg01147.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65766 Bug ID: 65766 Summary: gFortran Compiler SEGFAULTING on compiling simple program Product: gcc Version: 4.9.2 Status: UNCONFIRMED Severity: major Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: giorgianb at gmail dot com Created attachment 35315 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35315&action=edit Program that leads to gfortran SEGFAULTING The problem is that when using gfortran to compile a simple program (the source code for the program is attached) on the Raspberry Pi 2, the compiler crashes, giving this error message: bash-4.2$ gfortran-4.9 7.f95 f951: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See for instructions. Some version info from gfortran-4.9: bash-4.2$ gfortran-4.9 --version GNU Fortran (Raspbian 4.9.2-10) 4.9.2 Copyright (C) 2014 Free Software Foundation, Inc. GNU Fortran comes with NO WARRANTY, to the extent permitted by law. You may redistribute copies of GNU Fortran under the terms of the GNU General Public License. For more information about these matters, see the file named COPY Running the program uname -a to give some info: bash-4.2$ uname -a Linux raspberrypi 3.18.10-v7+ #774 SMP PREEMPT Wed Mar 25 14:10:30 GMT 2015 armv7l GNU/Linux Running gfortran-4.9 in valgrind hints to an unsupported system call: bash-4.2$ valgrind gfortran-4.9 7.f95 ==5539== Memcheck, a memory error detector ==5539== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==5539== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==5539== Command: gfortran-4.9 7.f95 ==5539== --5539-- WARNING: unhandled syscall: 369 --5539-- You may be able to write your own handler. --5539-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --5539-- Nevertheless we consider this a bug. Please report --5539-- it at http://valgrind.org/support/bug_reports.html. --5539-- WARNING: unhandled syscall: 369 --5539-- You may be able to write your own handler. --5539-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --5539-- Nevertheless we consider this a bug. Please report --5539-- it at http://valgrind.org/support/bug_reports.html. f951: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See for instructions. ==5539== ==5539== HEAP SUMMARY: ==5539== in use at exit: 41,873 bytes in 89 blocks ==5539== total heap usage: 218 allocs, 129 frees, 52,452 bytes allocated ==5539== ==5539== LEAK SUMMARY: ==5539== definitely lost: 5,337 bytes in 34 blocks ==5539== indirectly lost: 16 bytes in 1 blocks ==5539== possibly lost: 0 bytes in 0 blocks ==5539== still reachable: 36,520 bytes in 54 blocks ==5539== suppressed: 0 bytes in 0 blocks ==5539== Rerun with --leak-check=full to see details of leaked memory ==5539== ==5539== For counts of detected and suppressed errors, rerun with: -v ==5539== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Thank you for your time. I appreciate the GNU community's effort into producing good compilers. Giorgian