2018-05-24 20:44:18 +08:00
|
|
|
//===-- SystemInitializerLLGS.h ---------------------------------*- C++ -*-===//
|
|
|
|
//
|
2019-01-19 16:50:56 +08:00
|
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
2018-05-24 20:44:18 +08:00
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
2020-02-18 07:57:45 +08:00
|
|
|
#ifndef LLDB_TOOLS_LLDB_SERVER_SYSTEMINITIALIZERLLGS_H
|
|
|
|
#define LLDB_TOOLS_LLDB_SERVER_SYSTEMINITIALIZERLLGS_H
|
2018-05-24 20:44:18 +08:00
|
|
|
|
2018-12-04 01:28:29 +08:00
|
|
|
#include "lldb/Initialization/SystemInitializer.h"
|
2018-05-24 20:44:18 +08:00
|
|
|
#include "lldb/Initialization/SystemInitializerCommon.h"
|
|
|
|
|
|
|
|
class SystemInitializerLLGS : public lldb_private::SystemInitializerCommon {
|
|
|
|
public:
|
[lldb] Fix shared library directory computation on windows
Our code for locating the shared library directory works via dladdr (or
the windows equivalent) to locate the path of an address known to reside
in liblldb. This works great for C++ programs, but there's a catch.
When (lib)lldb is used from python (like in our test suite), this dladdr
call will return a path to the _lldb.so (or such) file in the python
directory. To compensate for this, we have code which attempts to
resolve this symlink, to ensure we get the canonical location. However,
here's the second catch.
On windows, this file is not a symlink (but a copy), so this logic
fails. Since most of our other paths are derived from the liblldb
location, all of these paths will be wrong, when running the test suite.
One effect of this was the failure to find lldb-server in D96202.
To fix this issue, I add some windows-specific code to locate the
liblldb directory. Since it cannot rely on symlinks, it works by
manually walking the directory tree -- essentially doing the opposite of
what we do when computing the python directory.
To avoid python leaking back into the host code, I implement this with
the help of a callback which can be passed to HostInfo::Initialize in
order to assist with the directory location. The callback lives inside
the python plugin.
I also strenghten the existing path test to ensure the returned path is
the right one.
Differential Revision: https://reviews.llvm.org/D96779
2021-02-16 04:51:32 +08:00
|
|
|
SystemInitializerLLGS() : SystemInitializerCommon(nullptr) {}
|
|
|
|
|
2019-02-22 06:26:16 +08:00
|
|
|
llvm::Error Initialize() override;
|
2018-05-24 20:44:18 +08:00
|
|
|
void Terminate() override;
|
|
|
|
};
|
|
|
|
|
2020-02-18 07:57:45 +08:00
|
|
|
#endif // LLDB_TOOLS_LLDB_SERVER_SYSTEMINITIALIZERLLGS_H
|