Skip to content

[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

Merged
merged 2 commits into from
Nov 14, 2024

Conversation

slydiman
Copy link
Contributor

@slydiman slydiman commented Jun 2, 2024

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.

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`.
@slydiman slydiman requested a review from JDevlieghere as a code owner June 2, 2024 17:41
@llvmbot llvmbot added the lldb label Jun 2, 2024
@llvmbot
Copy link
Member

llvmbot commented Jun 2, 2024

@llvm/pr-subscribers-lldb

Author: Dmitry Vasilyev (slydiman)

Changes

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-&gt;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://&lt;ip&gt;:&lt;port&gt;

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.


Full diff: https://github.com/llvm/llvm-project/pull/94165.diff

1 Files Affected:

  • (modified) lldb/test/Shell/Minidump/Windows/find-module.test (+2)
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" \

@slydiman slydiman marked this pull request as draft June 3, 2024 15:50
@slydiman slydiman closed this Oct 10, 2024
@slydiman slydiman reopened this Nov 13, 2024
@slydiman slydiman marked this pull request as ready for review November 13, 2024 18:22
@slydiman
Copy link
Contributor Author

It is the last show stopper
https://lab.llvm.org/staging/#/builders/197/builds/289

Copy link
Collaborator

@labath labath left a 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.

@slydiman slydiman merged commit 3d3b0bc into llvm:main Nov 14, 2024
6 checks passed
slydiman added a commit to slydiman/llvm-project that referenced this pull request Nov 14, 2024
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
slydiman added a commit that referenced this pull request Nov 14, 2024
Changing from UNSUPPOERTED to XFAIL in #94165 break x86 linux host /
Aarch64 linux target build
https://lab.llvm.org/buildbot/#/builders/195/builds/1047
@slydiman slydiman deleted the fix-lldb-find-module.test branch April 18, 2025 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants