David Blaikie 19fb98da55 PR19553: Memory leak in RuntimeDyldELF::createObjectImageFromFile ... This starts in MCJIT::getSymbolAddress where the unique_ptr<object::Binary> is release()d and (after a cast) passed to a single caller, MCJIT::addObjectFile. addObjectFile calls RuntimeDyld::loadObject. RuntimeDld::loadObject calls RuntimeDyldELF::createObjectFromFile And the pointer is never owned at this point. I say this point, because the alternative codepath, RuntimeDyldMachO::createObjectFile certainly does take ownership, so this seemed like a good hint that this was a/the right place to take ownership. llvm-svn: 207580		2014-04-29 21:52:46 +00:00
..
ChildTarget
Unix	[C++] Use 'nullptr'.	2014-04-28 04:05:08 +00:00
Windows
CMakeLists.txt
lli.cpp	PR19553: Memory leak in RuntimeDyldELF::createObjectImageFromFile	2014-04-29 21:52:46 +00:00
LLVMBuild.txt
Makefile
RemoteMemoryManager.cpp	[C++] Use 'nullptr'. Tools edition.	2014-04-25 04:24:47 +00:00
RemoteMemoryManager.h	[C++] Use 'nullptr'.	2014-04-28 04:05:08 +00:00
RemoteTarget.cpp	[C++] Use 'nullptr'. Tools edition.	2014-04-25 04:24:47 +00:00
RemoteTarget.h
RemoteTargetExternal.cpp	[Modules] Make Support/Debug.h modular. This requires it to not change	2014-04-21 22:55:11 +00:00
RemoteTargetExternal.h
RemoteTargetMessage.h
RPCChannel.h