The regular expression command object was resetting the execution context of the
resolved command, which it should not do.  It should adopt whatever context the
regular expression command was called with.  This was causing regular expression
commands run inside breakpoint commands to adopt the currently selected context,
not the one coming from the breakpoint that we hit.

<rdar://problem/13411771>


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@177195 91177308-0d34-0410-b5e6-96231b3b80d8
Make the conditional break test case a little more robust.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@177196 91177308-0d34-0410-b5e6-96231b3b80d8
Rework TestChangedValueAPI.py to account for gcc setting multiple breakpoints.


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