[patch] `set scheduler-locking step' made compatible with PPC atomic seqs

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

Hi,

if you set `set scheduler-locking step' it will still lock up despite the
recently accepted atomic sequences stepper if any software watchpoint exists.
It will start stepping and never let the other thread free the thread locks.
Such lockup should occur only during manual `step', not due to a watchpoint.
Red Hat is using default `set scheduler-locking step' (before it got
implemented upstream there was such implicit mode by a custom patch).

The first patch implements the fix as a minimal changeset assuming free `int'
<-> `enum resume_step' interchange.  The second patch implements the same
functionality by changing all the GDB code to the `enum resume_step' style
- provided only as a preview, patch is obsolete and a ChangeLog entry would
need to be included, upon request.

Attached also a testcase.


Regards,
Jan

Attachment: gdb-6.6-scheduler_locking-step-sw-watchpoints4.patch
Description: Text document

Attachment: gdb-6.6-ppc-atomic-sequence-test1.patch
Description: Text document

Attachment: step-cooked.patch
Description: Text document