<html>
<head>
<base href="http://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Figure out a better strategy for thread safety between the debugger thread"
href="http://llvm.org/bugs/show_bug.cgi?id=22108">22108</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Figure out a better strategy for thread safety between the debugger thread
</td>
</tr>
<tr>
<th>Product</th>
<td>lldb
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>All Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>lldb-dev@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Reporter</th>
<td>zturner@google.com
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>Right now the strategy is to stick a lock in every method of ProcessWindows
where there might be contention. This leads to difficult to analyze
situations, and it's not clear if the current mutex locations are either
necessary or sufficient to protect against race conditions. <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Clean up MSVC specific files in the test directories"
href="show_bug.cgi?id=21883">Bug 21883</a>, for
example, was caused by a race condition where the main thread acquired a lock,
signalled the debugger thread to do something and then wait for it to complete.
But the "do something" acquired the same lock, so it never completed.
There may be a better strategy, such as posting events to a message queue, etc
that make these issues go away.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>