Greg Clayton 762f7135e2 Don't put modules for .o files into the global shared module list. We ... used to do this because we needed to find the shared pointer for a .o file when the .o file's module was needed in a SymbolContext since the module in a symbol context was a shared pointer. Now that we are using intrusive pointers we don't have this limitation anymore since any instrusive shared pointer can be made from a pointer to an object all on its own. Also switched over to having the Module and SymbolVendor use shared pointers to their object files as had a leak on MacOSX when the SymbolVendor's object file wasn't the same as the Module's (debug info in a stand along file (dSYM file)). Now everything will correctly clean itself up when the module goes away after an executable gets rebuilt. Now we correctly get rid of .o files that are used with the DWARF with debug map executables on subsequent runs since the only shared pointer to the object files in from the DWARF symbol file debug map parser, and when the module gets replaced, it destroys to old one along with all .o files. Also added a small optimization when using BSD archives where we will remove old BSD containers from the shared list when they are outdated. llvm-svn: 140002		2011-09-18 18:59:15 +00:00
..
Makefile	Merged Eli Friedman's linux build changes where he added Makefile files that	2010-07-09 20:39:50 +00:00
SymbolVendorMacOSX.cpp	Don't put modules for .o files into the global shared module list. We	2011-09-18 18:59:15 +00:00
SymbolVendorMacOSX.h	LLDB now has "Platform" plug-ins. Platform plug-ins are plug-ins that provide	2011-03-08 22:40:15 +00:00