[Lldb-commits] [lldb] [lldb][riscv] Fix setting breakpoint for undecoded instruction (PR #90075)

[via lldb-commits]

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 8ef5c98e9f9276f09c590e22ab88a20ae86f3859...a8ee2a2ee75fcfac96a45796d0675eaa89c1aca6 lldb/test/API/riscv/break-undecoded/TestBreakpointIllegal.py
``````````

</details>

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

``````````diff
--- TestBreakpointIllegal.py	2024-06-07 08:23:24.000000 +0000
+++ TestBreakpointIllegal.py	2024-06-07 08:28:04.356595 +0000
@@ -28,12 +28,11 @@
 
     @skipIf(archs=no_match(["rv64gc"]))
     def test_2(self):
         self.build(dictionary={"C_SOURCES": "compressed.c", "EXE": "compressed.x"})
         (target, process, cur_thread, bkpt) = lldbutil.run_to_source_breakpoint(
-            self, "main", lldb.SBFileSpec("compressed.c"),
-            exe_name="compressed.x"
+            self, "main", lldb.SBFileSpec("compressed.c"), exe_name="compressed.x"
         )
         self.runCmd("thread step-inst")
         # we need to step more, as some compilers do not set appropriate debug info.
         while cur_thread.GetStopDescription(256) == "instruction step into":
             self.runCmd("thread step-inst")

``````````

</details>


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