From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10491 invoked by alias); 13 Sep 2011 20:32:42 -0000 Received: (qmail 10475 invoked by uid 22791); 13 Sep 2011 20:32:39 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 13 Sep 2011 20:32:26 +0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/50378] MALLOC_CHECK_ glibc detects free() invalid pointer in compiler Date: Tue, 13 Sep 2011 21:37: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-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 X-SW-Source: 2011-09/txt/msg00927.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50378 --- Comment #7 from Tobias Burnus 2011-09-13 20:31:26 UTC --- (In reply to comment #4) > I thought I had the latest version of gfortran... > Where can I find the latest one, with sources? While 4.6.1 (released 2011-08-17) is the latest stable release, you should use the latest branch ("gcc-4_6-branch") or the development version (trunk, 4.7). They are available via Subversion (http://gcc.gnu.org/svn.html), GIT (http://gcc.gnu.org/git/?p=gcc.git) and as regular (weekly?) source snapshots. Additionally, there exists also binary builds. See http://gcc.gnu.org/wiki/GFortranBinaries for a link to the binaries and (at the bottom) some pieces of information/links for building GCC from source. It makes sense to report bugs against the current gcc-4_6-branch or 4.7 as those contain all the existing fixes, which will be part in the next release. Also Linux distributions tend to base their GCC packages on the release branches and not on the releases from the release branch.