This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: MI *stopped reason

From: Bob Rossi <bob at brasko dot net>
To: Konstantin Karganov <kostik at ispras dot ru>
Cc: Daniel Jacobowitz <drow at false dot org>, gdb at sources dot redhat dot com
Date: Thu, 14 Jul 2005 10:39:57 -0400
Subject: Re: MI *stopped reason
References: <20050713134630.GA3283@nevyn.them.org> <Pine.LNX.4.44.0507141801580.29233-100000@ispserv.ispras.ru>

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

References:
- Re: GDB is stepping past main()
  - From: Daniel Jacobowitz
- MI *stopped reason
  - From: Konstantin Karganov

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]