From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21789 invoked by alias); 5 Feb 2009 09:25:11 -0000 Received: (qmail 21779 invoked by uid 22791); 5 Feb 2009 09:25:10 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 05 Feb 2009 09:25:05 +0000 Received: (qmail 26117 invoked from network); 5 Feb 2009 09:25:03 -0000 Received: from unknown (HELO wind.local) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 5 Feb 2009 09:25:03 -0000 From: Vladimir Prus To: teawater Subject: Re: MI *stopped versus silent breakpoint Date: Thu, 05 Feb 2009 09:25:00 -0000 User-Agent: KMail/1.9.10 Cc: Marc Khouzam , Pedro Alves , gdb@sourceware.org References: <6D19CA8D71C89C43A057926FE0D4ADAA06CB0F19@ecamlmw720.eamcs.ericsson.se> <6D19CA8D71C89C43A057926FE0D4ADAA04E1BF53@ecamlmw720.eamcs.ericsson.se> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902051225.41426.vladimir@codesourcery.com> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-02/txt/msg00036.txt.bz2 On Thursday 05 February 2009 11:09:56 teawater wrote: > Hi Marc, > > I read the source code in infcmd.c:finish_backward. > This is because function "proceed" will be call twice in > "finish_backward". Maybe MI output depend some > observer_notify_target_xxx function. So it output twice. The *stopped notification is output as result of call to observer_notify_normal_stop which is done in infrun.c:normal_stop. I do believe that "silent" breakpoint should generate *stopped, since otherwise frontend will assume the target is running. Furthermore, I believe that silent breakpoints, in MI, should behave identically to ordinary breakpoints -- as it stands, we print *stopped without frame information. I don't know why a silent breakpoint is used in implementation of reverse-finish, nor do I understand why normal_stop is called in the middle of reverse-finish when stopping on that temporary breakpoint. I think the first fix it to make reverse-finish not to call normal_stop on that internal breakpoint (just like normal_stop is not called on solib load breakpoint). - Volodya