diff options
| author | Hafiz Abid Qadeer <hafiz_abid@mentor.com> | 2015-02-04 09:59:23 +0000 |
|---|---|---|
| committer | Hafiz Abid Qadeer <hafiz_abid@mentor.com> | 2015-02-04 09:59:23 +0000 |
| commit | d1f606ff0f6b73df512a4526763f8e3cfebbc690 (patch) | |
| tree | e737759ac5e9b7489f50bb93f1af002f5469dae1 /llvm/test/CodeGen/ARM/memcpy-inline.ll | |
| parent | 22b1525ae8f9ed24b18dbde833fb18f4fd5d52c0 (diff) | |
| download | bcm5719-llvm-d1f606ff0f6b73df512a4526763f8e3cfebbc690.tar.gz bcm5719-llvm-d1f606ff0f6b73df512a4526763f8e3cfebbc690.zip | |
Fix a race condition in lldb-mi.
lldb-mi has 3 threads.
1. One that waits for user intput.
2. Another waits for 1st thread to get input command.
3. Waits for events from lldb.
2 & 3 needs to be synchronized so that they don't end up
doing things at same time. For example, while "break insert" is
processing, we can get a breakpoint event. Depending on where we
are in "break-insert", it can have different behavior. In some
cases, it can cause breakpoint to be deleted too. I have added a
mutex so that command processing and event processing are done
exclusively and they are not running at the same time.
In longer term, I think thread 2 & 3 should be merged to be only
one thread which can wait on command or events.
Reviewed in http://reviews.llvm.org/D7371.
llvm-svn: 228128
Diffstat (limited to 'llvm/test/CodeGen/ARM/memcpy-inline.ll')
0 files changed, 0 insertions, 0 deletions

