>SIGTRAP bug to me which is fixed by the above.
>
>To elaborate on the problem: right now we have two ways of specifying a
>thread to the remote agent. Hg specifies the "general" thread, and Hc
>specifies the "continue" thread. These correspond to inferior_ptid and
>resume_ptid, roughly.
>
>When we single-step, if we are not using some form of
>scheduler-locking, resume_ptid is 0. We don't tell the agent at that
>point what inferior_ptid is; it has to step _some_ thread, and it picks
>one, and if it doesn't pick the one GDB expected we get problems.