aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/ExtractAPI/Serialization/SymbolGraphSerializer.cpp
diff options
context:
space:
mode:
authorDave Lee <davelee.com@gmail.com>2022-07-08 17:34:10 -0700
committerDave Lee <davelee.com@gmail.com>2022-07-13 16:56:53 -0700
commitb5ccfeb6bfbbc5436b91a1e317f88e2c499c9306 (patch)
tree8a9cde6385077a5a4c4fdee9534b35fd7f200b41 /clang/lib/ExtractAPI/Serialization/SymbolGraphSerializer.cpp
parentbe68a6adfba29b275272cb36e606bc0cb08518b3 (diff)
downloadllvm-b5ccfeb6bfbbc5436b91a1e317f88e2c499c9306.zip
llvm-b5ccfeb6bfbbc5436b91a1e317f88e2c499c9306.tar.gz
llvm-b5ccfeb6bfbbc5436b91a1e317f88e2c499c9306.tar.bz2
[lldb] Add image dump pcm-info command
Add `pcm-info` to the `target module dump` subcommands. This dump command shows information about clang .pcm files. This command effectively runs `clang -module-file-info` and produces identical output. The .pcm file format is tightly coupled to the clang version. The clang embedded in lldb is not guaranteed to match the version of the clang executable available on the local system. There have been times when I've needed to view the details about a .pcm file produced by lldb's embedded clang, but because the clang executable was a slightly different version, the `-module-file-info` invocation failed. With this command, users can inspect .pcm files generated by lldb too. Differential Revision: https://reviews.llvm.org/D129456
Diffstat (limited to 'clang/lib/ExtractAPI/Serialization/SymbolGraphSerializer.cpp')
0 files changed, 0 insertions, 0 deletions