-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[lldb] Disable find-module.test in case of a remote target #94165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The target arch is `i386-pc-windows` after loading the dump. It updates to `i386-pc-windows-msvc` or `i386-pc-windows-gnu` in lldb\source\Plugins\Process\minidump\ProcessMinidump.cpp, line 218 ``` GetTarget().MergeArchitecture(module->GetArchitecture()); ``` But in case of the remote target (`remote-linux`) and the `Windows host` lldb executed the following commands at the beginning ``` platform select remote-linux platform connect connect://<ip>:<port> ``` and then the target arch is `i386-pc-windows-msvc` immediately after loading the dump. GetTarget().MergeArchitecture(module->GetArchitecture()) does not update it to `i386-pc-windows-gnu` when the module arch is `i386-pc-windows-gnu`.
@llvm/pr-subscribers-lldb Author: Dmitry Vasilyev (slydiman) ChangesThe target arch is
But in case of the remote target (
and then the target arch is Full diff: https://github.com/llvm/llvm-project/pull/94165.diff 1 Files Affected:
diff --git a/lldb/test/Shell/Minidump/Windows/find-module.test b/lldb/test/Shell/Minidump/Windows/find-module.test
index 7ac2f74f8039b..b3a7ec36520f0 100644
--- a/lldb/test/Shell/Minidump/Windows/find-module.test
+++ b/lldb/test/Shell/Minidump/Windows/find-module.test
@@ -1,6 +1,8 @@
Test that we correctly find a PE/COFF file in our executable search path, and
use it when opening minidumps.
+UNSUPPORTED: remote{{.*}}
+
RUN: yaml2obj %S/Inputs/find-module.exe.yaml -o %T/find-module.exe
RUN: yaml2obj %S/Inputs/find-module.dmp.yaml -o %T/find-module.dmp
RUN: %lldb -O "settings set target.exec-search-paths %T" \
|
It is the last show stopper |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
XFAIL would probably be better as this sounds like something that should work.
Co-authored-by: Pavel Labath <[email protected]>
Changing from UNSUPPOERTED to XFAIL in llvm#94165 break x86 linux host / Aarch64 linux target build https://lab.llvm.org/buildbot/#/builders/195/builds/1047
Changing from UNSUPPOERTED to XFAIL in #94165 break x86 linux host / Aarch64 linux target build https://lab.llvm.org/buildbot/#/builders/195/builds/1047
The target arch is
i386-pc-windows
after loading the dump. It updates toi386-pc-windows-msvc
ori386-pc-windows-gnu
in lldb\source\Plugins\Process\minidump\ProcessMinidump.cpp, line 218But in case of the remote target (
remote-linux
) and theWindows host
lldb executed the following commands at the beginningand then the target arch is
i386-pc-windows-msvc
immediately after loading the dump. GetTarget().MergeArchitecture(module->GetArchitecture()) does not update it toi386-pc-windows-gnu
when the module arch isi386-pc-windows-gnu
.