Greg Clayton 9b5442aed9 Now that the command interpreter runs in a separate thread in Xcode, we need to lock the target API lock instead of trying to lock it.
What was happening was:
1 - Xcode ran and stopped and was doing work on thread 2
2 - Users would type something in Xcode console on thread 1
3 - thread 3 would be running command interpreter thread and try to execute command but get "failed to get API lock" error for any command that wanted the target API lock (like "expression")

<rdar://problem/15775016>

llvm-svn: 200997
2014-02-07 22:31:20 +00:00
..
2013-11-07 00:11:47 +00:00
2013-09-25 10:37:32 +00:00
2013-06-17 22:51:50 +00:00
2013-02-20 23:51:13 +00:00
2013-09-05 16:42:23 +00:00
2013-09-05 16:42:23 +00:00
2013-09-05 16:42:23 +00:00
2013-09-05 16:42:23 +00:00
2013-09-05 16:42:23 +00:00
2013-09-05 16:42:23 +00:00
2013-09-05 16:42:23 +00:00
2013-09-05 16:42:23 +00:00
2013-09-05 16:42:23 +00:00
2013-09-05 16:42:23 +00:00
2012-08-29 21:13:06 +00:00
2013-01-28 23:47:25 +00:00