PT_CONTINUE and PT_STEP are process-scope on FreeBSD

Although ptrace() can be passed a PID or TID for PT_CONTINUE and PT_STEP,
the kernel operates on all threads in the process in both cases.  (See
the FOREACH_THREAD_IN_PROC in FreeBSD's sys_process.c:kern_ptrace.)

Make this clear by using the PID from the ProcessMonitor instance.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@195656 91177308-0d34-0410-b5e6-96231b3b80d8
Fix issue from r166732 found by Andrew Kaylor

From Jim Ingham's email:
  It does look like ThreadPlanStepInRange test is some kind of thinko.
  In practice, in this case it is probably safe to run only one thread
  when doing the "step through" since that generally involved running
  from a shared library stub to its target.  That could deadlock if the
  dynamic loader has to fix up the symbol, and another thread is in the
  middle of doing that.  But that doesn't seem to be very common, or at
  least the code is clearly wrong but I haven't had any reports of this
  causing deadlocks...


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@195657 91177308-0d34-0410-b5e6-96231b3b80d8