From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-289815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 12118 invoked by alias); 27 Jul 2009 19:27:39 -0000
Received: (qmail 12080 invoked by uid 48); 27 Jul 2009 19:27:24 -0000
Date: Mon, 27 Jul 2009 19:27:00 -0000
Subject: [Bug fortran/40877]  New: memory leaks with gfc_charlen?
X-Bugzilla-Reason: CC
Message-ID: <bug-40877-16146@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
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
X-SW-Source: 2009-07/txt/msg02196.txt.bz2

This PR is a reminder to check some places where a new gfc_charlen is allocated
without properly setting it into a namelist (ns->cl_list). Each of them may
potentially produce a memory leak (though I'm not completely sure):

 * expr.c (simplify_const_ref)
 * symbol.c (gfc_set_default_type, generate_isocbinding_symbol)
 * trans-decl.c (create_function_arglist)

I noticed them while working on PR40822, where I also introduced the function
gfc_new_charlen, which should be used instead of gfc_get_charlen to avoid
memory leaks.


-- 
           Summary: memory leaks with gfc_charlen?
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: janus at gcc dot gnu dot org


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