[all-commits] [llvm/llvm-project] b5ccfe: [lldb] Add image dump pcm-info command

[Dave Lee via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: b5ccfeb6bfbbc5436b91a1e317f88e2c499c9306
      https://github.com/llvm/llvm-project/commit/b5ccfeb6bfbbc5436b91a1e317f88e2c499c9306
  Author: Dave Lee <davelee.com at gmail.com>
  Date:   2022-07-13 (Wed, 13 Jul 2022)

  Changed paths:
    M clang/include/clang/Frontend/FrontendActions.h
    M clang/lib/Frontend/FrontendActions.cpp
    M lldb/source/Commands/CommandObjectTarget.cpp
    A lldb/test/API/commands/target/dump-pcm-info/Makefile
    A lldb/test/API/commands/target/dump-pcm-info/TestDumpPCMInfo.py
    A lldb/test/API/commands/target/dump-pcm-info/main.m

  Log Message:
  -----------
  [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