From: Eli Zaretskii <eliz@gnu.org>
To: Natalia Saiapova <natalia.saiapova@intel.com>
Cc: gdb-patches@sourceware.org, tankut.baris.aktemur@intel.com
Subject: Re: [PATCH 6/6] gdb: add eval option to lock the scheduler during infcalls.
Date: Fri, 29 Dec 2023 14:06:31 +0200 [thread overview]
Message-ID: <83o7e95i2g.fsf@gnu.org> (raw)
In-Reply-To: <20231229104202.7878-7-natalia.saiapova@intel.com> (message from Natalia Saiapova on Fri, 29 Dec 2023 10:42:02 +0000)
> From: Natalia Saiapova <natalia.saiapova@intel.com>
> Cc: tankut.baris.aktemur@intel.com
> Date: Fri, 29 Dec 2023 10:42:02 +0000
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index bdbbadacb89..532179cdca1 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -18,16 +18,20 @@ disassemble
>
> * New commands
>
> -set scheduler-locking replay run | replay step | run | step (on|off)
> -show scheduler-locking (replay run | replay step | run | step)
> - Extend the scheduler locking settings with a set of set/show
> +set scheduler-locking eval | replay eval | replay run | replay step | run | step (on|off)
> +show scheduler-locking (eval | replay eval | replay run | replay step | run | step)
> + Extend the scheduler-locking settings with a set of set/show
> commands, which can be used individually to control the scheduler during
> various commands.
> - 'replay run' -- when on, the scheduler is locked during non-stepping
> + 'eval' -- when on, the scheduler is locked during expression evaluation
> + in normal mode.
Doesn't this affect only expression evaluation that calls functions in
the inferior? That is, commands like "print 2+2" will not be
affected, right? If I'm right, this should be mentioned in the
documentation.
Thanks.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
prev parent reply other threads:[~2023-12-29 12:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 10:41 [PATCH 0/6] Refinement of scheduler-locking settings Natalia Saiapova
2023-12-29 10:41 ` [PATCH 1/6] gdb: use schedlock_applies in user_visible_resume_ptid Natalia Saiapova
2024-02-08 18:50 ` Tom Tromey
2023-12-29 10:41 ` [PATCH 2/6] gdb, cli: remove left-over code from "set_logging_on" Natalia Saiapova
2024-02-08 18:50 ` Tom Tromey
2023-12-29 10:41 ` [PATCH 3/6] gdb, cli: pass the argument of a set command to its callback Natalia Saiapova
2024-02-08 18:45 ` Tom Tromey
2023-12-29 10:42 ` [PATCH 4/6] gdb: change the internal representation of scheduler locking Natalia Saiapova
2023-12-29 11:49 ` Eli Zaretskii
2023-12-29 10:42 ` [PATCH 5/6] gdb: add commands to control " Natalia Saiapova
2023-12-29 12:03 ` Eli Zaretskii
2023-12-29 10:42 ` [PATCH 6/6] gdb: add eval option to lock the scheduler during infcalls Natalia Saiapova
2023-12-29 12:06 ` Eli Zaretskii [this message]
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=83o7e95i2g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=natalia.saiapova@intel.com \
--cc=tankut.baris.aktemur@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).