From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-22211-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 28496 invoked by alias); 14 Jul 2005 14:40:02 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 28470 invoked by uid 22791); 14 Jul 2005 14:39:59 -0000
Received: from lakermmtao05.cox.net (HELO lakermmtao05.cox.net) (68.230.240.34)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 14 Jul 2005 14:39:59 +0000
Received: from white ([68.9.64.121]) by lakermmtao05.cox.net
          (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP
          id <20050714143958.EUES19733.lakermmtao05.cox.net@white>;
          Thu, 14 Jul 2005 10:39:58 -0400
Received: from bob by white with local (Exim 3.35 #1 (Debian))
	id 1Dt4sX-0006BC-00; Thu, 14 Jul 2005 10:39:57 -0400
Date: Thu, 14 Jul 2005 14:40:00 -0000
From: Bob Rossi <bob@brasko.net>
To: Konstantin Karganov <kostik@ispras.ru>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sources.redhat.com
Subject: Re: MI *stopped reason
Message-ID: <20050714143957.GC23506@white>
Mail-Followup-To: Konstantin Karganov <kostik@ispras.ru>,
	Daniel Jacobowitz <drow@false.org>, gdb@sources.redhat.com
References: <20050713134630.GA3283@nevyn.them.org> <Pine.LNX.4.44.0507141801580.29233-100000@ispserv.ispras.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0507141801580.29233-100000@ispserv.ispras.ru>
User-Agent: Mutt/1.3.28i
X-SW-Source: 2005-07/txt/msg00174.txt.bz2

On Thu, Jul 14, 2005 at 06:12:55PM +0400, Konstantin Karganov wrote:
> Hello.
> 
> When the execution of the debuggee stops the debugger reports the result 
> as "*stopped, reason='...' ". I'd like to know if the reason should always 
> be specified, or not.
> Currently, there are cases when the reason is missing (for example, when 
> stopped on a temporary breakpoint).

I believe the reason should always be specified. Although there is no MI
standard that states it, right? If you know where to add the reason in
breakpoint.c simply add a new enumeration to
mi/mi-command.h:async_reply_reason. 

Without the reason, the front end is left a little confused as to what
happened.

Thanks,
Bob Rossi