[lldb/crashlog] Skip null image dsym fetching on interactive mode
authorMed Ismail Bennani <medismail.bennani@gmail.com>
Wed, 10 Aug 2022 00:31:31 +0000 (17:31 -0700)
committerMed Ismail Bennani <medismail.bennani@gmail.com>
Wed, 10 Aug 2022 04:01:37 +0000 (21:01 -0700)
commit355be8cf801603756520cf5d9b4b5eaf9d1b2e77
tree4c50d4da64a7d0bce378fbb559a1ab890293cc67
parent41c1a5f9bdc4cb6914e7971f50e4f45aeb11e087
[lldb/crashlog] Skip null image dsym fetching on interactive mode

Sometimes, it can happen that a crash report has null images in its list
of used binaries. This manifests like such:

```
    0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???
```

When fetching debug symbols to symbolicate the crashlog stackframe,
having null images causes `dsymForUUID` to hang for few seconds.

This patch addresses that by skipping null images from being load by the
scripted process.

rdar://97419487

Differential Revision: https://reviews.llvm.org/D131038

Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
lldb/examples/python/scripted_process/crashlog_scripted_process.py
lldb/test/Shell/ScriptInterpreter/Python/Crashlog/Inputs/interactive_crashlog/multithread-test.ips