A Monday 23 June 2008 02:03:53, Daniel Jacobowitz wrote:
> On Tue, Jun 17, 2008 at 07:24:04PM +0100, Pedro Alves wrote:
> > @@ -422,7 +417,10 @@ execute_command (char *p, int from_tty)
> >
> >        /* If the target is running, we allow only a limited set of
> >           commands. */
> > -      if (target_can_async_p () && target_executing && !get_cmd_async_ok
> > (c)) +      if (target_can_async_p ()
> > +	  && target_has_execution
> > +	  && any_running ()
> > +	  && !get_cmd_async_ok (c))
> >  	error (_("Cannot execute this command while the target is running."));
> >
> >        /* Pass null arg rather than an empty one.  */
>
> Don't need target_has_execution here anymore, do we?

That's correct.  I've fixed it.  I've also removed the stop_soon check
that you noticed I was dropping in a later patch in the series.  I
couldn't find a reason it is needed now.

> The patch otherwise looks OK.

Thanks.  Here's the updated patch that I'll commit unless there
are more comments to it.

-- 
Pedro Alves