From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-6787-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 2127 invoked by alias); 9 May 2009 20:05:59 -0000
Received: (qmail 2073 invoked by uid 48); 9 May 2009 20:05:59 -0000
Date: Sat, 09 May 2009 20:05:00 -0000
From: "gnu-bugs at the-morg dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Message-ID: <20090509200558.10137.gnu-bugs@the-morg.org>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug cli/10137] New: Memory Leak's PATCH included
X-Bugzilla-Reason: CC
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
X-SW-Source: 2009-q2/txt/msg00089.txt.bz2

Originally I was investigating a specific reproducible memory leak so I stuck
valgrind on GDB and fixed 3 or 4 leaks which show up clearly once you iterate
1000s of command via the MI protocol interface.

Version: 6.8.50.20090509-cvs

-- 
           Summary: Memory Leak's PATCH included
           Product: gdb
           Version: 6.8
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: cli
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: gnu-bugs at the-morg dot org
                CC: gdb-prs at sourceware dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=10137

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.