[lldb-dev] [Bug 22108] New: Figure out a better strategy for thread safety between the debugger thread

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Tue Jan 6 12:04:07 PST 2015


http://llvm.org/bugs/show_bug.cgi?id=22108

            Bug ID: 22108
           Summary: Figure out a better strategy for thread safety between
                    the debugger thread
           Product: lldb
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: lldb-dev at cs.uiuc.edu
          Reporter: zturner at google.com
    Classification: Unclassified

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.  Bug 21883, 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150106/62605d2e/attachment.html>


More information about the lldb-dev mailing list