[Lldb-commits] [lldb] [lldb] Fix breakpoint resolver serialization bug (PR #76766)

Greg Clayton via lldb-commits lldb-commits at lists.llvm.org
Wed Jan 3 15:48:06 PST 2024


clayborg wrote:

> ```
> ======================================================================
> ERROR: test_resolver_serialization (TestBreakpointSerialization.BreakpointSerialization)
>    Test that breakpoint resolvers contain the expected information
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\llvm-project\lldb\test\API\functionalities\breakpoint\serialize\TestBreakpointSerialization.py", line 60, in test_resolver_serialization
>     exe_module.IsValid(), "Failed to find the executable module in target"
>     ^^^^^^^^^^^^^^^^^^
> AttributeError: 'NoneType' object has no attribute 'IsValid'
> Config=aarch64-C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe
> ----------------------------------------------------------------------
> ```
> 
> @clayborg Any idea why the executable module wouldn't be found here? Looks like `exe_module` is `None`.

You can just use "a.out" when doing the lookup, do this:
```
exe_module = self.orig_target.module["a.out"]
```
The full path isn't needed. I would guess there might be some sort of path issue with the value returned from `self.getBuildArtifact("a.out")` that doesn't match exactly with the windows path from the module list?

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


More information about the lldb-commits mailing list