macOS: lldb-mi uses 100% when debugging GTESTs #9831

Activity

1. WardenGnaw commented on Sep 1, 2022

   

   Andrew Wang (WardenGnaw)

   on Sep 1, 2022

   Member

   More actions

   lldb-mi is an external tool we depend on. You can file an issue at https://github.com/lldb-tools/lldb-mi/issues
2. Andrew Wang (WardenGnaw)

   added

   external

   on Sep 1, 2022
3. Zingam commented on Sep 2, 2022

   

   Hristo Hristov (Zingam)

   on Sep 2, 2022

   More actions

   This looks just like lldb-tools/lldb-mi#101 (comment)
4. Hristo Hristov (H-G-Hristov)

   changed the title [-]macOS: lldb-mi uses 100% when debugging GTESTs, [/-] [+]macOS: lldb-mi uses 100% when debugging GTESTs[/+] on Sep 2, 2022
5. H-G-Hristov commented on Sep 7, 2022

   

   Hristo Hristov (H-G-Hristov)

   on Sep 7, 2022

   Author

   More actions

   It looks like I have had this issue on a Intel Mac on BigSur even a 1.5 years ago:
   #7105
6. H-G-Hristov commented on Sep 12, 2022

   

   Hristo Hristov (H-G-Hristov)

   on Sep 12, 2022

   Last edited by H-G-Hristov

   Author

   More actions

   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
         }
     ]
   }
   

   👍React with 👍5Reacted by luckyxiaoqiang, Rossi Sun, Nelson Goncalves, Db1zz and Joey_Yan

   👎React with 👎2Reacted by Ilya and Leo Auri
7. yanedge commented on Jun 16, 2023

   

   Yan (yanedge)

   on Jun 16, 2023

   More actions

   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"
       },    
   

   👍React with 👍1Reacted by Heiland
8. H-G-Hristov commented on Jun 17, 2023

   

   Hristo Hristov (H-G-Hristov)

   on Jun 17, 2023

   Last edited by H-G-Hristov

   Author

   More actions

   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?
9. yanedge commented on Jul 13, 2023

   

   Yan (yanedge)

   on Jul 13, 2023

   More actions

   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.

   👍React with 👍3Reacted by Hristo Hristov, Dmitry Shipilov and stardust
10. ee778 commented on Sep 21, 2025

    

    Guo Xiancong (ee778)

    on Sep 21, 2025

    More actions

    When debugging C++ code with version 1.104.1 of VSCode in macOS 26, it still causes a memory leak in lldb-mi.

    👍React with 👍1Reacted by Heiland
11. Bob Brown (bobbrow)

    marked Possible memory leak related to lldb-mi #10176 as a duplicate of this issue on Oct 10, 2025