macOS: lldb-mi uses 100% when debugging GTESTs

[H-G-Hristov]

Type: Bug

Im using the C++ TestMate extension

1. Place a breakpoint in a GTest
2. Run debugging on Unit test
3. The debugger stops on the breakpoint a spinner in Locals turns around indefinitely
4. Click continue, etc. nothing happens

If a breakpoint is placed in another file (non-GTest), debugging works.

Debugging can be stopped. After multiple starts and restarts there many
lldb-mi processes using 100% cpu.

Extension version: 1.12.4
VS Code version: Code 1.70.2 (Universal) (e4503b30fc78200f846c62cf8091b76ff5547662, 2022-08-16T05:36:37.829Z)
OS version: Darwin arm64 21.6.0
Modes:

System Info

Item	Value
CPUs	Apple M1 Pro (8 x 24)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled
Load (avg)	6, 32, 25
Memory (System)	16.00GB (1.90GB free)
Process Argv	--crash-reporter-id a7eaff19-94ae-4653-b917-d9aaab19da5d
Screen Reader	no
VM	0%

A/B Experiments

vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411cf:30557515
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
pylanb8912:30545647
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012cf:30540253
azure-dev_surveyone:30548225
i497e931:30553904

[WardenGnaw]

lldb-mi is an external tool we depend on. You can file an issue at https://github.com/lldb-tools/lldb-mi/issues

[Zingam]

This looks just like lldb-tools/lldb-mi#101 (comment)

[H-G-Hristov]

It looks like I have had this issue on a Intel Mac on BigSur even a 1.5 years ago:
#7105

[H-G-Hristov]

A workaround: #7240 (comment)
https://stackoverflow.com/questions/58329611/vscode-macos-catalina-doesnt-stop-on-breakpoints-on-c-c-debug/70991654#70991654

Use CodeLLDB:

{
  "version": "0.2.0",
  "configurations": [
      {
          //...other configuration
          "type": "lldb", // change this one from cppdbg to lldb
      }
  ]
}

[yanedge]

A workaround: #7240 (comment) https://stackoverflow.com/questions/58329611/vscode-macos-catalina-doesnt-stop-on-breakpoints-on-c-c-debug/70991654#70991654

Use CodeLLDB:

{
  "version": "0.2.0",
  "configurations": [
      {
          //...other configuration
          "type": "lldb", // change this one from cppdbg to lldb
      }
  ]
}

If you use cmake, add this to your settings.json

    "cmake.debugConfig": {
        "type": "lldb"
    },    

[H-G-Hristov]

A workaround: #7240 (comment) https://stackoverflow.com/questions/58329611/vscode-macos-catalina-doesnt-stop-on-breakpoints-on-c-c-debug/70991654#70991654
Use CodeLLDB:

{
  "version": "0.2.0",
  "configurations": [
      {
          //...other configuration
          "type": "lldb", // change this one from cppdbg to lldb
      }
  ]
}

If you use cmake, add this to your settings.json

    "cmake.debugConfig": {
        "type": "lldb"
    },    

Could you please add some context. Is it going to fix the lldb-mi issue with cpptools or does it do something else? Or is it for codelldb?

[yanedge]

A workaround: #7240 (comment) https://stackoverflow.com/questions/58329611/vscode-macos-catalina-doesnt-stop-on-breakpoints-on-c-c-debug/70991654#70991654
Use CodeLLDB:

{
  "version": "0.2.0",
  "configurations": [
      {
          //...other configuration
          "type": "lldb", // change this one from cppdbg to lldb
      }
  ]
}

If you use cmake, add this to your settings.json

    "cmake.debugConfig": {
        "type": "lldb"
    },    

Could you please add some context. Is it going to fix the lldb-mi issue with cpptools or does it do something else? Or is it for codelldb?

it is for codelldb.