Greg Clayton cc4d0146b4 This checking is part one of trying to add some threading safety to our ... 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		2012-02-17 07:49:44 +00:00
..
ItaniumABILanguageRuntime.cpp	This checking is part one of trying to add some threading safety to our	2012-02-17 07:49:44 +00:00
ItaniumABILanguageRuntime.h	Change "frame var" over to using OptionGroups (and thus the OptionGroupVariableObjectDisplay).	2011-05-04 03:43:18 +00:00
Makefile	Add the LanguageRuntime plugins to the makefile build, and remove the	2011-05-19 23:44:09 +00:00