gdb-remote: use elaborated type specifier for `Module`
authorSaleem Abdulrasool <compnerd@compnerd.org>
Wed, 5 Dec 2018 04:04:14 +0000 (04:04 +0000)
committerSaleem Abdulrasool <compnerd@compnerd.org>
Wed, 5 Dec 2018 04:04:14 +0000 (04:04 +0000)
When building with MSVC, the type `Module` is ambiguous due to both the
lldb_private and llvm namespaces being used.  Use the elaborated type
instead to resolve the ambiguity.

llvm-svn: 348332

lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp

index 7225a39..5959d9b 100644 (file)
@@ -683,7 +683,7 @@ void ProcessGDBRemote::BuildDynamicRegisterInfo(bool force) {
   m_register_info.Finalize(GetTarget().GetArchitecture());
 }
 
-Status ProcessGDBRemote::WillLaunch(Module *module) {
+Status ProcessGDBRemote::WillLaunch(lldb_private::Module *module) {
   return WillLaunchOrAttach();
 }
 
@@ -799,7 +799,7 @@ Status ProcessGDBRemote::WillLaunchOrAttach() {
 //----------------------------------------------------------------------
 // Process Control
 //----------------------------------------------------------------------
-Status ProcessGDBRemote::DoLaunch(Module *exe_module,
+Status ProcessGDBRemote::DoLaunch(lldb_private::Module *exe_module,
                                   ProcessLaunchInfo &launch_info) {
   Log *log(ProcessGDBRemoteLog::GetLogIfAllCategoriesSet(GDBR_LOG_PROCESS));
   Status error;