Skip to content
  • Greg Clayton's avatar
    This checking is part one of trying to add some threading safety to our · cc4d0146
    Greg Clayton authored
    internals. The first part of this is to use a new class:
    
    lldb_private::ExecutionContextRef
    
    This class holds onto weak pointers to the target, process, thread and frame
    and it also contains the thread ID and frame Stack ID in case the thread and
    frame objects go away and come back as new objects that represent the same
    logical thread/frame. 
    
    ExecutionContextRef objcets have accessors to access shared pointers for
    the target, process, thread and frame which might return NULL if the backing
    object is no longer available. This allows for references to persistent program
    state without needing to hold a shared pointer to each object and potentially
    keeping that object around for longer than it needs to be. 
    
    You can also "Lock" and ExecutionContextRef (which contains weak pointers)
    object into an ExecutionContext (which contains strong, or shared pointers)
    with code like
    
    ExecutionContext exe_ctx (my_obj->GetExectionContextRef().Lock());
    
    llvm-svn: 150801
    cc4d0146
Loading