Skip to content

RolandMa1986/vscode-lldb

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

799 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Abaut

While learning CLR Runtime, I found it's hardly to understand how the context is switched between Managed and Nitave Code.

When I choose codelldb or cppdbg debugger to launch the app(in vscode), I can neither set the breakpoint on C# code, nor see the Managed CallStack.

You can not get Native frames if you are using coreclr debugger.

SOS

Sometimes I will use SOS plugin with lldb. but all the command was executed outside of the vscode. So why not bring codelldb and sos together?

Changes

  • When initializing the lldb. SOS will be loaded.
  • Check file's extention. use bpmd command instead if it's a cs file.
  • Try find managed frame by IP2MD command if no source code is found when breakpoint is hit.

Quick Start

Here's a minimal debug configuration to get you started:

{
    "lldb.launch.debugServer": 4711,
    "lldb.launch.initCommands": [
        "plugin load /home/path/to/sos/libsosplugin.so",
        "setsymbolserver -ms"
    ],
}

Links

About

This is a vscode debugger plugin forked from vadimcn/vscode-lldb. with Dotnet Mixed debug mode of Native and Managed code. It's very helpfull while learning CLR runime. You can easily switch csharp and cpp context with it.

Resources

License

Stars

0 stars

Watchers

0 watching

Forks

Packages

 
 
 

Contributors

Languages

  • C++ 38.6%
  • Rust 36.7%
  • TypeScript 12.0%
  • C 5.2%
  • Python 5.1%
  • CMake 2.1%
  • Other 0.3%