[Lldb-commits] [lldb] [lldb][Windows] Don't synthesise a fake thread name from the executable (PR #199983)

via lldb-commits lldb-commits at lists.llvm.org
Wed May 27 09:08:29 PDT 2026


github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {darker}-->


:warning: Python code formatter, darker found issues in your code. :warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
darker --check --diff -r origin/main...HEAD lldb/test/API/windows/thread/TestThreadName.py
``````````

:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:

</details>

<details>
<summary>
View the diff from darker here.
</summary>

``````````diff
--- TestThreadName.py	2026-05-27 16:06:31.000000 +0000
+++ TestThreadName.py	2026-05-27 16:07:43.123400 +0000
@@ -18,11 +18,12 @@
 
         target, process, thread, bkpt = lldbutil.run_to_source_breakpoint(
             self, "// break here", source
         )
         self.assertEqual(
-            bkpt.GetNumLocations(), 2,
+            bkpt.GetNumLocations(),
+            2,
             "expected breakpoints at both '// break here' markers",
         )
 
         # No thread name yet.
         self.assertFalse(

``````````

</details>


https://github.com/llvm/llvm-project/pull/199983


More information about the lldb-commits mailing list