Cold-Air-Networks/mirror-llvm-project
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 7
mirror-llvm-project/lldb/test/API/windows/launch/missing-dll/TestMissingDll.py

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

30 lines
1 KiB
Python
Raw Normal View History

[LLDB] Show exit code on Windows if process can't launch (#141290) When running a process that would exit before LLDB could stop the target, it would try to interpret (and subsequently format) the exit code as a Win32 error. However, processes on Windows won't return Win32 errors in that case. They will often return an [NTSTATUS](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55). One common case for this to occur is when a DLL is missing. In that case, the process will start successfully, but it will exit with `STATUS_DLL_NOT_FOUND`. LLDB would previously return "unknown error", because it tried to [`FormatMessage`](https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-formatmessage) `0xC0000135` which doesn't work, so it fell back to "unknown error". This PR changes the error to be the string "Process prematurely exited with {0:x}" and doesn't try to format the exit code. One could `FormatMessage` an `NTSTATUS` by passing `FORMAT_MESSAGE_FROM_HMODULE` and a handle to `ntdll.dll`, however, I don't think we can get the required format arguments (e.g. the missing DLL name - `%hs`).
2025-05-27 12:16:03 -08:00
import lldb
from lldbsuite.test.decorators import *
from lldbsuite.test.lldbtest import *
from lldbsuite.test import lldbutil
[lldb] Decorate tests that use shared libraries (#193118) `wasip1` does not support shared libraries in the traditional POSIX sense. It was designed primarily as a monolithic system interface for standalone modules where everything is statically linked. `wasip2` introduced a "component model" where components achieve the goals of shared libraries.
2026-04-29 08:57:55 -08:00
@skipIfTargetDoesNotSupportSharedLibraries()
[LLDB] Show exit code on Windows if process can't launch (#141290) When running a process that would exit before LLDB could stop the target, it would try to interpret (and subsequently format) the exit code as a Win32 error. However, processes on Windows won't return Win32 errors in that case. They will often return an [NTSTATUS](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55). One common case for this to occur is when a DLL is missing. In that case, the process will start successfully, but it will exit with `STATUS_DLL_NOT_FOUND`. LLDB would previously return "unknown error", because it tried to [`FormatMessage`](https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-formatmessage) `0xC0000135` which doesn't work, so it fell back to "unknown error". This PR changes the error to be the string "Process prematurely exited with {0:x}" and doesn't try to format the exit code. One could `FormatMessage` an `NTSTATUS` by passing `FORMAT_MESSAGE_FROM_HMODULE` and a handle to `ntdll.dll`, however, I don't think we can get the required format arguments (e.g. the missing DLL name - `%hs`).
2025-05-27 12:16:03 -08:00
class MissingDllTestCase(TestBase):
[lldb] Introduce the require decorator (#212753) Currently, it is unclear if a test that is skipped is either: - Unsupported because it will never run (macosx tests should not run on Windows). - Skipped because it's supposed to work but does not yet. `@expectedFailure` is not always an option because a test might be timing out and waiting 600s for it to fail is not acceptable. This patch introduces 2 new decorators to differentiate those tests: - `@requireX` meaning the tests require X to run (e.g `@requireDarwin`). - `@requireNotX` meaning the tests requires anything but `X` to run (e.g `@requireNotDarwin`). In the tests results summary, this introduces a new category: `skipped` tests: - `@requireX` -> `UNSUPPORTED` - `@skipIfX` -> `SKIPPED` Here is how they can and cannot be stacked: This will never run: ```py3 @requireDarwin @requireWindows def test(): ... ``` This will not run on Linux, because `@requireWindows` is not satisfied. ```py3 @requireNotDarwin @requireWindows def test(): ... ``` For "require Darwin or Windows", you need: ```py3 @requirePlatform(["darwin", "windows"]) def test(): ... ``` For "require Darwin on ARM64 or Windows on ARM64", you need: ```py3 @requireARM64 @requirePlatform(["darwin", "windows"]) def test(): ... ``` This patch also converts the tests in `lldb/tests/API/{macosx,linux,windows}` to use these decorators. Patches to convert the rest of the tests will follow.
2026-08-01 08:03:29 -08:00
@requireWindows
[LLDB] Show exit code on Windows if process can't launch (#141290) When running a process that would exit before LLDB could stop the target, it would try to interpret (and subsequently format) the exit code as a Win32 error. However, processes on Windows won't return Win32 errors in that case. They will often return an [NTSTATUS](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55). One common case for this to occur is when a DLL is missing. In that case, the process will start successfully, but it will exit with `STATUS_DLL_NOT_FOUND`. LLDB would previously return "unknown error", because it tried to [`FormatMessage`](https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-formatmessage) `0xC0000135` which doesn't work, so it fell back to "unknown error". This PR changes the error to be the string "Process prematurely exited with {0:x}" and doesn't try to format the exit code. One could `FormatMessage` an `NTSTATUS` by passing `FORMAT_MESSAGE_FROM_HMODULE` and a handle to `ntdll.dll`, however, I don't think we can get the required format arguments (e.g. the missing DLL name - `%hs`).
2025-05-27 12:16:03 -08:00
def test(self):
"""
Test that lldb reports the application's exit code (STATUS_DLL_NOT_FOUND),
rather than trying to treat it as a Win32 error number.
"""
self.build()
exe = self.getBuildArtifact("a.out")
dll = self.getBuildArtifact("dummy_dll.dll")
self.assertTrue(remove_file(dll))
target = self.dbg.CreateTarget(exe)
self.assertTrue(target, VALID_TARGET)
launch_info = lldb.SBLaunchInfo(None)
launch_info.SetWorkingDirectory(self.get_process_working_directory())
error = lldb.SBError()
target.Launch(launch_info, error)
[lldb][windows] relax TestMissingDll.py assert (#199046)
2026-05-21 07:24:37 -08:00
self.assertFalse(error.Success(), "expected launch to fail")
self.assertIn("Process prematurely exited with 0xc0000135", error.GetCString())
Reference in a new issue Copy permalink