From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: pfee@talk21.com
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] stept, nextt, finisht, untilt, continuet
Date: Tue, 30 Aug 2011 11:56:00 -0000 [thread overview]
Message-ID: <20110830115627.GA21003@host1.jankratochvil.net> (raw)
In-Reply-To: <1314698487.57217.YahooMailRC@web86705.mail.ird.yahoo.com>
On Tue, 30 Aug 2011 12:01:27 +0200, pfee@talk21.com wrote:
> I like the 'step' mode of scheduler-locking, but often wish it applied to the
> "next" command, not just step.
I agree, it does not apply to the continue-over-call part of `next'. But that
is a bug which should be fixed.
> My suggestion would be to create a "set scheduler-locking next" mode in which
> both "step" and "next" operate with other threads locked out.
Do you think the "step" mode would be still useful if "next" exists?
Thanks,
Jan
next prev parent reply other threads:[~2011-08-30 11:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 1:49 Doug Evans
2011-08-30 9:16 ` Jan Kratochvil
2011-08-30 10:01 ` pfee
2011-08-30 11:56 ` Jan Kratochvil [this message]
2011-08-30 12:42 ` pfee
2011-08-30 14:21 ` Jan Kratochvil
2011-08-30 15:09 ` Doug Evans
2011-08-30 15:22 ` Pedro Alves
2011-08-30 17:13 ` Tom Tromey
2011-08-30 17:29 ` Pedro Alves
2011-09-02 16:48 ` Doug Evans
2011-08-30 17:00 ` Tom Tromey
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=20110830115627.GA21003@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pfee@talk21.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