rchamala wrote: In my case, for non-scripted process of coredump, I see the module information even when symbol is not found and I see a placeholder object being created for the module. For scripted process, it shows only the main module due to the limitation I pointed in this PR
Target 1 is child elf-core process target. Target 2 is scripted process target 1. **Current State (without my change)** Target list ``` Current targets: target #0: <none> ( platform=host ) target #1: [vdso] ( arch=aarch64-*-linux, platform=remote-android, pid=1234, state=stopped ) * target #2: /path/to/coredump ( arch=aarch64-*-*, platform=remote-android, pid=3456, state=stopped ) ``` 2. Sample Image List of child elf-core target. Note the `*` at the end, which indicates placeholder object ``` [0] 0x1234455 [vdso] /path/to/a.out [1] 0x1234566 /path/to/libc.so(*) [2] ... ``` 3. Sample Image list of scripted process target. Only one module is shown ``` [0] 0x1234445 [vdso] /path/to/a.out ``` **With my PR to ignore load module errors:** 1. Sample image list of scripted process target. All modules are shown, for the ones whose symbols are not found, place holder objects are created similar to non-scripted process targets ``` [0] 0x1234455 [vdso] /path/to/a.out [1] 0x1234566 /path/to/libc.so(*) [2] 0x1245666 /path/to/libb.so [3] ... ``` https://github.com/llvm/llvm-project/pull/127153 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
