Failed to load MI Debugger about envoy HOT 11 CLOSED

Failed to load MI Debugger:Dwarf Error: wrong unit_type in
compilation unit header (is DW_UT_split_compile (0x05), should be DW_UT_type (0x02)) [in module/build/.cache/bazel/_bazel_vscode/-2d35de14639eaad1ac7060a4dd7e3351/execroot/envoy/bazel-out/k8- dbg/bin/source/exe/_objs/envoy_main_entry_lib/main.pic.dwo](from file-exec-and-symbols "/build/.cache/bazel/_bazel_vscode/-2d35de14639eaad1ac7060a4dd7e3351/execroot/envoy/bazel-out/k8- dbg/bin/source/exe/envoy-static")

from envoy.

How can I fix this error?

from envoy.

from envoy.

could you try the lldb? Seems that the current build flags is not friendly to the gdb.

from envoy.

cc @phlax @keith

from envoy.

could you try the lldb? Seems that the current build flags is not friendly to the gdb.

@wbpcode I tried debugging with lldb, but it causes a spike in my Docker CPU usage, eventually leading to unresponsiveness in Docker.

from envoy.

gcc version could be a factor (from reading this https://sourceware.org/bugzilla/show_bug.cgi?id=27354)

what version are you testing with? is it >= 11.1 ? is it the gcc in the envoy build container - which i think is 11.4?

from envoy.

Seems it works in our local env.

1.VScode configuration:
{
"version": "0.2.0",
"configurations": [
{
"name": "Debug Envoy",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/bazel-bin/source/exe/envoy-static",
"args": ["-c", "path/to/your/envoy.yaml"],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
}
]
}

2.Make sure GDB was installed on your host.
I faced the same "MIDebuggerPath" issue. But after re-install the gdb , vscode debug works well.

from envoy.

gcc version could be a factor (from reading this https://sourceware.org/bugzilla/show_bug.cgi?id=27354)

what version are you testing with? is it >= 11.1 ? is it the gcc in the envoy build container - which i think is 11.4?

@phlax Thank you. I think this is the reason for the error. However, this image is provided by Envoy. I hope you can fix this issue. I will fix it in my local image first.

from envoy.

However, this image is provided by Envoy.

i suspect you need to rebuild your vscode env or similar - the current Envoy image contains gcc 11.4

from envoy.

After upgrading gdb to 11.2, this issue has been resolved. Thanks everyone for your help.
@phlax @wbpcode @wufanqqfsc

from envoy.