Re: [RFC] stept, nextt, finisht, untilt, continuet

[Jan Kratochvil <jan dot kratochvil at redhat dot com>]

On Tue, 30 Aug 2011 14:41:49 +0200, pfee@talk21.com wrote:
> Another point, regarding "continue".  In non-stop mode, there's a "-a" flag to 
> continue all threads.  Would it be worth using the same flag when in 
> scheduler-locking mode to cause the entire process to resume?

One can use `set scheduler-locking off' in such case.

The point of `set scheduler-locking step' is that it should affect the most
common uses of GDB.  Stepping/Nexting single thread but continue-ing all the
threads.

One can alwaye use `set scheduler-locking' as an override if s/he has some
specific needs.

My original post was that I believe the new `*t' commands were invented more
because `set scheduler-locking step' is not default+working.  I guess such
idea would not arise at all otherwise.  Any new configuration options and/or
more commands are bad when the same functionality can be reached otherwise.


Thanks,
Jan