From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3250 invoked by alias); 6 Mar 2008 19:48:04 -0000 Received: (qmail 3216 invoked by uid 71); 6 Mar 2008 19:48:01 -0000 Date: Thu, 06 Mar 2008 19:48:00 -0000 Message-ID: <20080306194801.3215.qmail@sourceware.org> To: nobody@sources.redhat.com Cc: gdb-prs@sources.redhat.com, From: Nick Roberts Subject: Re: gdb/2426: Temporary breakpoint for "finish" command not cleaned up in MI mode Reply-To: Nick Roberts Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2008-q1/txt/msg00071.txt.bz2 The following reply was made to PR gdb/2426; it has been noted by GNATS. From: Nick Roberts To: tom.fowler@hotmail.co.uk Cc: gdb-gnats@sources.redhat.com Subject: Re: gdb/2426: Temporary breakpoint for "finish" command not cleaned up in MI mode Date: Fri, 7 Mar 2008 08:43:19 +1300 > The "finish" command appears to work by setting a temporary breakpoint which > is deleted immediately after it is triggered. Using my version of GDB in > normal console mode this works as expected, but using the same executable in > "--interpreter=mi" mode, the "finish" command leaves its breakpoint around > to fire spuriously later on. Having looked into this a little, it seems to > be a regression, in that the problem does not occur for an earlier version > of GDB (v 6.0.x). Looks like it's fixed in GDB in the Sourceware CVS repository. If you can't get this, GDB 6.8 should be released very shortly. -- Nick http://www.inet.net.nz/~nickrob