VSCode lldb Can't Inspect Variables

[guoyuanchao1202]

container OS:

VSCode Version: 1.71.2 (Universal)
CodeLLDB Version: v 1.7.4
Compiler: clang 14.0.0

Debuggee: C++ Project-Envoy

I use vscode-remote container debug Envoy, I can debug normally but i can't inspect any variables while debugging.
debug:

launch.json:

        {
            "name": "lldb //source/exe:envoy-static",
            "program": "/build/.cache/bazel/_bazel_vscode/2d35de14639eaad1ac7060a4dd7e3351/execroot/envoy/bazel-out/k8-dbg/bin/source/exe/envoy-static",
            "sourceMap": {
                "/proc/self/cwd": "/workspaces/envoy",
                "/proc/self/cwd/external": "/build/envoy-compdb/_bazel_vscode/2d35de14639eaad1ac7060a4dd7e3351/execroot/envoy/external",
                "/proc/self/cwd/bazel-out": "/build/envoy-compdb/_bazel_vscode/2d35de14639eaad1ac7060a4dd7e3351/execroot/envoy/bazel-out"
            },
            "cwd": "${workspaceFolder}",
            "args": [
                "-c",
                "envoy-config.json"
            ],
            "type": "lldb",
            "request": "launch"
        }

I've tried many things and can't get it to work, can anyone help me?
Many thanks

Verbose log

[vadimcn]

Please make sure you are compiling in debug mode.

[guoyuanchao1202]

Please make sure you are compiling in debug mode.

yeah, the command I use is bazel build -c dbg, but not work..i don't know why:)

[erikjoh]

I had the same issue and I think I've figured it out.
By default, bazel will use --fission dbg which will:

Enables Fission, which writes C++ debug information to dedicated .dwo files instead of .o files, where it would otherwise go. This substantially reduces the input size to links and can reduce link times.

Under the hood, I think it will use -gsplit-dwarf.

Since the majority of the debug info ends up in envoy-static.dwp and vscode-lldb / lldb doesn't find this file automatically we aren't able to inspect the variables.
When compiling Envoy like this though bazel build --fission=no -c dbg //source/exe:envoy-static , I am finally able to inspect variables.
I think it would be nice if there's some way to make lldb also read/load the envoy-static.dwp file so that we don't have to disable fission.

[vadimcn]

I think it's this: llvm/llvm-project#28667