From: Vladimir Prus <vladimir@codesourcery.com>
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [MI non-stop 05/11, RFA] -exec-continue/-exec-interrupt --all
Date: Sun, 29 Jun 2008 17:37:00 -0000 [thread overview]
Message-ID: <200806291008.17770.vladimir@codesourcery.com> (raw)
In-Reply-To: <m3skuxl8lp.fsf@fleche.redhat.com>
On Saturday 28 June 2008 22:25:54 Tom Tromey wrote:
> >>>>> "Vladimir" == Vladimir Prus <vladimir@codesourcery.com> writes:
>
> Vladimir> Per MI non-stop spec, continue and interrupt need --all option
> Vladimir> to resume every thread. Implemented thusly. OK?
>
> Vladimir> +void
> Vladimir> +interrupt_target_1 (int all_threads)
> Vladimir> +{
> Vladimir> + if (non_stop)
> Vladimir> + {
>
> It looks to me like there are 2 extra indentation spaces in this
> function's body.
You're right, I've fixed this.
- Volodya
next prev parent reply other threads:[~2008-06-29 6:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 16:56 Vladimir Prus
2008-06-28 18:17 ` Marc Khouzam
2008-06-29 6:05 ` Vladimir Prus
2008-06-28 20:28 ` Tom Tromey
2008-06-29 17:37 ` Vladimir Prus [this message]
2008-07-11 13:34 ` Daniel Jacobowitz
2008-07-13 4:25 ` Daniel Jacobowitz
2008-07-13 4:36 ` Vladimir Prus
2008-07-13 14:32 ` Daniel Jacobowitz
2008-07-13 16:24 ` Vladimir Prus
2008-07-13 22:35 ` Nick Roberts
2008-07-13 5:50 ` Vladimir Prus
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=200806291008.17770.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@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