Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Async mode fixes.
Date: Fri, 14 Mar 2008 18:58:00 -0000	[thread overview]
Message-ID: <200803142158.18959.vladimir@codesourcery.com> (raw)
In-Reply-To: <20080314182629.GD31663@caradoc.them.org>

On Friday 14 March 2008 21:26:29 Daniel Jacobowitz wrote:
> On Wed, Mar 05, 2008 at 10:27:28AM +0300, Vladimir Prus wrote:
> > +	  /* If any exception escaped to here, we better enable
> > +	     stdin.  Otherwise, any command that calls async_disable_stdin,
> > +	     and the can throw, will leave stdin inoperable.  */
> 
> and can throw?

"and then throws", actually.
> 
> >      case INF_EXEC_COMPLETE:
> > -      /* Is there anything left to do for the command issued to
> > -         complete? */
> > +
> > +      /* This is the first thing to do -- so that continuations know that
> > +	 the target is stopped.  For example, command_line_handler_continuation
> > +	 will run breakpoint commands, and if we thing that the target is
> > +	 running, we'll refuse to execute most command.  MI continuation
> > +	 presently is target_executing to either print or not print *stopped.  */
> > +      target_executing = 0;
> 
> "if we think", "most commands".  "is" -> "uses" in the last line, right?

right.


> 
> > @@ -1005,10 +1006,28 @@ static void
> >  signal_command (char *signum_exp, int from_tty)
> 
> Two spaces after periods in this function :-)
> 
> > +/* Do any commands attached to breakpoint we stopped at. Only if we
> > +   are always running synchronously. Or if we have just executed a
> > +   command that doesn't start the target. */
> 
> Here too.
> 
> > +static void
> > +command_line_handler_continuation (struct continuation_arg *arg)
> > +{
> > +  extern int display_time;
> > +  extern int display_space;
> > +
> > +  long time_at_cmd_start  = arg->data.longint;
> > +  long space_at_cmd_start = arg->next->data.longint;
> > +
> > +  bpstat_do_actions (&stop_bpstat);
> > +  /*do_cleanups (old_chain); *//*?????FIXME????? */
> 
> Clean up this, please.

Oh, this is not mine, I've just moved command_line_handler_continuation
to a different module. Anyway, some of later patches of mine removes
that line as not necessary, and I might as well do it now.

> 
> Other than that, this can go in now.  Thanks.  Between you and Nick
> and Pedro I'm sure we'll have async mode working again soon.

Thanks, checked in.

- Volodya
 



  reply	other threads:[~2008-03-14 18:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  7:27 Vladimir Prus
2008-03-07 22:19 ` Nick Roberts
2008-03-07 22:33   ` Daniel Jacobowitz
2008-03-08  8:16     ` Vladimir Prus
2008-03-08  8:59   ` Vladimir Prus
2008-03-08 20:36     ` Nick Roberts
2008-03-08 20:54       ` Daniel Jacobowitz
2008-03-08 23:09         ` Nick Roberts
2008-03-09  0:01           ` Daniel Jacobowitz
2008-03-10  7:58       ` Vladimir Prus
2008-03-10  9:12         ` Nick Roberts
2008-03-10 10:02           ` Vladimir Prus
2008-03-10 22:06             ` Nick Roberts
2008-03-14 18:26 ` Daniel Jacobowitz
2008-03-14 18:58   ` Vladimir Prus [this message]
2008-03-17 14:11 ` [commit] Fix compile error (Re: [RFA] Async mode fixes.) Ulrich Weigand
2008-03-17 14:17   ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200803142158.18959.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox