maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Revert "Implement basic DidAttach and DidLaunch for DynamicLoaderWindowsDYLD." 

This reverts commit 7749a10ddbe22767d0e055753c674fcde7f28d39.

This commit introduces about 15-20 new test failures with windows local
targets.

llvm-svn: 245765
This commit is contained in:
Zachary Turner 2015-08-21 23:57:25 +00:00
parent f56872dc30
commit 21708cf970
1 changed files with 0 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
lldb/source/Plugins/DynamicLoader/Windows-DYLD/DynamicLoaderWindowsDYLD.cpp
View File

@ -9,7 +9,6 @@
#include "DynamicLoaderWindowsDYLD.h"
#include "lldb/Core/Log.h"
#include "lldb/Core/PluginManager.h"
#include "lldb/Target/Process.h"
#include "lldb/Target/Target.h"
@ -73,38 +72,11 @@ DynamicLoaderWindowsDYLD::CreateInstance(Process *process, bool force)
void
DynamicLoaderWindowsDYLD::DidAttach()
{
Log *log(GetLogIfAnyCategoriesSet(LIBLLDB_LOG_DYNAMIC_LOADER));
if (log)
log->Printf("DynamicLoaderWindowsDYLD::%s()", __FUNCTION__);
DidLaunch();
m_process->LoadModules();
}
void
DynamicLoaderWindowsDYLD::DidLaunch()
{
Log *log(GetLogIfAnyCategoriesSet(LIBLLDB_LOG_DYNAMIC_LOADER));
if (log)
log->Printf("DynamicLoaderWindowsDYLD::%s()", __FUNCTION__);
ModuleSP executable = GetTargetExecutable();
if (!executable.get())
return;
ModuleList module_list;
module_list.Append(executable);
// FIXME: We probably should not always use 0 as the load address
// here. Testing showed that when debugging a process that we start
// ourselves, there's no randomization of the load address of the
// main module, therefore an offset of 0 will be valid.
// If we attach to an already running process, this is probably
// going to be wrong and we'll have to get the load address somehow.
UpdateLoadedSections(executable, LLDB_INVALID_ADDRESS, 0);
m_process->GetTarget().ModulesDidLoad(module_list);
}
Error