This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH 0/4] Make "set scheduler-locking step" depend on user intention, only
- From: Pedro Alves <palves at redhat dot com>
- To: gdb-patches at sourceware dot org
- Date: Tue, 24 Mar 2015 18:07:33 +0000
- Subject: Re: [PATCH 0/4] Make "set scheduler-locking step" depend on user intention, only
- Authentication-results: sourceware.org; auth=none
- References: <1426084798-1032-1-git-send-email-palves at redhat dot com>
On 03/11/2015 02:39 PM, Pedro Alves wrote:
> Currently, "set scheduler-locking step" is a bit odd. The manual
> documents it as being optimized for stepping, so that focus of
> debugging does not change unexpectedly, but then it says that
> sometimes other threads may run, and thus focus may indeed change
> unexpectedly... A user can then be excused to get confused and wonder
> why does GDB behave like this.
> I don't think a user should have to know about details of how "next"
> or whatever other run control command is implemented internally to
> understand when does the "scheduler-locking step" setting take effect.
> Thus this series makes "set scheduler-locking step" hold threads
> depending on whether the _command_ the user entered was a stepping
> command [step/stepi/next/nexti], or not. More details in patch #3.
> The rest of the series is related groundwork and cleaning up.
> Tested on x86_64 Fedora 20, native and gdbserver.
I pushed this in now.