Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Klaus Gerlicher <klaus.gerlicher@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v6 5/6] gdb: refine commands to control scheduler locking.
Date: Wed, 04 Feb 2026 16:25:21 +0200	[thread overview]
Message-ID: <86bji4zium.fsf@gnu.org> (raw)
In-Reply-To: <20260204133753.547281-6-klaus.gerlicher@intel.com> (message from Klaus Gerlicher on Wed, 4 Feb 2026 13:37:52 +0000)

> From: Klaus Gerlicher <klaus.gerlicher@intel.com>
> Date: Wed,  4 Feb 2026 13:37:52 +0000
> 
>  gdb/NEWS                                      |  21 ++
>  gdb/doc/gdb.texinfo                           |  66 +++++-
>  gdb/infrun.c                                  | 224 ++++++++++++++----
>  .../gdb.mi/user-selected-context-sync.exp     |  22 +-
>  .../gdb.threads/hand-call-in-threads.exp      |  10 +-
>  .../multiple-successive-infcall.exp           |   6 +-
>  gdb/testsuite/gdb.threads/schedlock.exp       |  80 ++++++-
>  gdb/testsuite/lib/gdb.exp                     |  70 ++++--
>  8 files changed, 397 insertions(+), 102 deletions(-)

Thanks.

> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -749,6 +749,27 @@ list .
>    lines.  This makes it more obvious that there is no information, as opposed
>    to implying there is no inferior loaded.
>  
> +set scheduler-locking <command type> (on|off)
> +show scheduler-locking <command type>
> +  where <command-type> is one of the following:
> +    continue | replay continue | replay step | step.
> +  Extend the scheduler locking settings with a set of set/show
> +  commands, which can be used individually to control the scheduler during
> +  stepping and continuing commands.  Stepping commands include step, stepi,
> +  next. Continuing commands include continue, finish, until, jump, return.
         ^^
Two spaces there, please.

> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo

This part is okay.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2026-02-04 14:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 13:37 [PATCH v6 0/6] gdb: refine scheduler locking settings Klaus Gerlicher
2026-02-04 13:37 ` [PATCH v6 1/6] gdb: use schedlock_applies in user_visible_resume_ptid Klaus Gerlicher
2026-02-04 13:37 ` [PATCH v6 2/6] gdb, cli: remove left-over code from "set_logging_on" Klaus Gerlicher
2026-02-04 14:13   ` Gerlicher, Klaus
2026-02-04 13:37 ` [PATCH v6 3/6] gdb, cli: pass the argument of a set command to its callback Klaus Gerlicher
2026-02-04 13:37 ` [PATCH v6 4/6] gdb: change the internal representation of scheduler locking Klaus Gerlicher
2026-02-04 13:37 ` [PATCH v6 5/6] gdb: refine commands to control " Klaus Gerlicher
2026-02-04 14:25   ` Eli Zaretskii [this message]
2026-02-04 13:37 ` [PATCH v6 6/6] gdb: add eval option to lock the scheduler during infcalls Klaus Gerlicher
2026-02-04 14:22   ` Eli Zaretskii
2026-02-17  9:03 ` [PATCH v6 0/6] gdb: refine scheduler locking settings Gerlicher, Klaus
2026-03-03  8:15   ` Gerlicher, Klaus

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=86bji4zium.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=klaus.gerlicher@intel.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