diff options
| author | Greg Clayton <gclayton@apple.com> | 2014-02-07 22:31:20 +0000 |
|---|---|---|
| committer | Greg Clayton <gclayton@apple.com> | 2014-02-07 22:31:20 +0000 |
| commit | 9b5442aed9858419dd12f622d763d7a92a92020f (patch) | |
| tree | 4e28065ddc02cbee6c29930929e0595400584bfc /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | 41c440fbfea9112d4e8a9dfd8c851fe39a04525d (diff) | |
| download | llvm-9b5442aed9858419dd12f622d763d7a92a92020f.zip llvm-9b5442aed9858419dd12f622d763d7a92a92020f.tar.gz llvm-9b5442aed9858419dd12f622d763d7a92a92020f.tar.bz2 | |
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
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions