All Versions
79
Latest Version
Avg Release Cycle
28 days
Latest Release
-

Changelog History
Page 4

  • v1.4.1-dev

    October 20, 2019
  • v1.4.0 Changes

    October 20, 2019

    ๐Ÿ”„ Changed

    ๐Ÿ†• New

    • Added support for data breakpoints.
    • โž• Added "Attach to Process..." command for quick attaching without having to create a debug configuration.
    • โž• Added URL handler for [starting a debug session from outside of VSCode](MANUAL.md#starting-debug-session-outside-of-vscode). Rust users: please take note - I believe this may provide a more convenient way of debugging the unit tests.
  • v1.3.0 Changes

    July 15, 2019

    ๐Ÿ›  Fixed

    • ๐Ÿ Redirection to the integrated terminal now works on Windows too.

    ๐Ÿ”„ Changed

    • ๐Ÿ”ง Native adapter is now the default. You can still use 'classic' or 'bundle' by setting the lldb.adapterType configuration option.
    • 0๏ธโƒฃ "integrated" is now the default value for the "terminal" launch config property.

    ๐Ÿ†• New

    • ๐Ÿ–จ Loaded modules viewlet: rather than printing loaded modules notifications in the Debug Console view, modules are now displayed in a separate tab in the Debug view.
    • 0๏ธโƒฃ lldb.consoleMode setting, which controls whether the debug console input is by default treated as debugger commands or as expressions to evaluate.
    • Added support for Jump to to cursor command (thanks @ntoskrnl7!).
  • v1.2.4

    May 06, 2019
  • v1.2.3 Changes

    May 06, 2019

    ๐Ÿ†• New

    • ๐Ÿ†• New UI for display settings (status bar and "Display Options..." command).
    • โž• Added support for configurable external LLDB backends (native adapter only).

    ๐Ÿ”„ Changed

    • โšก๏ธ Updated bundled LLDB to v8.0 final.

    ๐Ÿ›  Fixed

    • ๐Ÿ› Bug #173 - Debugger module is not auto-imported when native adapter is used.
    • Native adapter panics in rare cases when formatting Python tracebacks.
  • v1.2.2 Changes

    March 30, 2019

    ๐Ÿ›  Fixed

    • ๐Ÿ”ง Debug configuration generation from Cargo.toml when using recent Cargo versions.

    ๐Ÿ›  Fixed (native adapter only)

    • LLDB command completions inserting duplicate tokens in some cases.
    • Remote debugging when using QEMU debug stub.
    • Spurious stop events at the beginning of a debug session.

    ๐Ÿ†• New (native adapter only)

    • Implemented hit conditions on breakpoints.
    • โšก๏ธ More informative error messages when displaying optimized-out variables, invalid pointers, etc.
    • Announce executed scripts (e.g. initCommands, preRunCommands), for easier attribution of script errors.
    • ๐Ÿ‘Œ Support ",[<number>]" format specifier, which reinterprets the displayed value as an array of <number> elements.

    Heads up: CodeLLDB is moving to native code.

    Up until now, CodeLLDB's debug adapter has been based on whatever version of the LLDB was installed on the local machine, with Python scripts providing the glue between LLDB API and VS Code. This arrangement has its benefits: the extension can be very compact and platform-independent. The flip side of using an externally-provided LLDB, is that it may happen to be quite old and buggy. There had been quite a few problems reported because of that. I've also been somewhat ๐ŸŽ dissatisfied with CodeLLDB's performance and stability, which I attribute to the use of Python in a project that has long grown past being "just a simple script".

    As a consequence, I've decided to try a new approach:

    • Pre-built LLDB binaries will be provided with the extension. This will ensure that it is used with the same ๐Ÿ”– version of LLDB engine as it was tested with. (In order to reduce the download size, native binaries will not be included ๐Ÿ“ฆ in the initial installation package published on VS Code Marketplace. Instead, a smaller, platform-targeted package will be downloaded on first use.)
    • Most of Python code had been ported to a statically-typed compiled language (Rust).

    For now, both implementations of the debug adapter will exist in parallel. You can choose which one is used by setting lldb.adapterType to either classic or native in your workspace settings. 0๏ธโƒฃ In a few versions, I plan to make native the default, and then, eventually, the only option.

    Please give the native adapter a try and let me know how that worked for you, and, especially, if it didn't. Thanks!

  • v1.2.1 Changes

    February 03, 2019

    ๐Ÿ”„ Changed

    • ๐Ÿ‘ The minimum supported VSCode version is now 1.30.

    ๐Ÿ›  Fixed

    • Source maps.
    • ๐Ÿ Python detection on Windows.
    • Debug adapter process is sometimes left running after the end of a debug session.
    • Adjusted Rust visualizer for libstd changes in v1.33.
  • v1.2.0 Changes

    December 29, 2018

    ๐Ÿ†• New

    • [Beta] Introduced "bundled" and "native" debug adapter types (in addition to "classic"): if lldb.adapterType confguration ๐Ÿ— setting is set to either of those values, CodeLLDB will download and use a custom build of LLDB and use it instead of the system-provided one.

    ๐Ÿ›  Fixed

    • ๐Ÿ›  Misc bug fixes.
  • v1.2.0-alpha

    November 25, 2018
  • v1.1.2

    November 25, 2018