profile
viewpoint

vadimcn/cargo-pgo 24

Supercharge you Rust programs!

vadimcn/llvm 12

Temporary fork of LLVM for Rust

vadimcn/compiler-rt 3

Mirror of official compiler-rt git repository located at http://llvm.org/git/compiler-rt. Updated hourly.

vadimcn/rust 2

a safe, concurrent, practical language

vadimcn/awesome-rust 1

A curated list of Rust code and resources.

vadimcn/clang 0

Mirror of official clang git repository located at http://llvm.org/git/clang. Updated every five minutes.

vadimcn/compiler-builtins 0

Porting `compiler-rt` intrinsics to Rust

issue commentvadimcn/vscode-lldb

LLDB10.0 from Swift5.3 crashes at start

Python 2 won't work Did you try pointing to python3?

damuellen

comment created time in 14 hours

issue commentvadimcn/vscode-lldb

Support for Rust NDarray

Please see lldb formatters docs.

selvavm

comment created time in 14 hours

issue commentvadimcn/vscode-lldb

Breakpoints Not Stopping (Rust, MacOS)

The breakpoints in main.rs aren't getting resolved. Are you building with debug info?

dan-fritchman

comment created time in 14 hours

PR opened indygreg/python-build-standalone

Add cross-builds for ARM

This enables cross-building for aarch64-unknown-linux-gnu and arm-unknown-linux-gnueabihf. Because Python runs various scripts in the course of install image generation, a host arch Python distribution needs to be built first.

Areas that still need work:

  • I've changed the base image to ubuntu:xenial, because it has cross-toolchains readily available. Obviously, a Python distro built that way may not run on older Linuxes, e.g. CentOS 6 and the like.
  • Not all Python tests pass. But then they didn't seem to pass before my changes either. Am I running tests the wrong way? -
    (PYTHONHOME=$(pwd)/install LD_LIBRARY_PATH=$(pwd)/install/lib $(pwd)/install/bin/python3 build/run_tests.py from the root of extracted zstd package).
  • I could not get the pip module to work on arm - python3 -m ensurepip fails because of missing _sysconfigdata__linux_aarch64-linux-gnu module. Not sure why it isn't getting built...
+192 -87

0 comment

33 changed files

pr created time in 17 hours

push eventvadimcn/python-build-standalone

Vadim Chugunov

commit sha 113927cf141dd3ecd94612d4324caa040118c069

cross-builds for ARM

view details

push time in 17 hours

create barnchvadimcn/python-build-standalone

branch : cross-builds

created branch time in 21 hours

fork vadimcn/python-build-standalone

Produce redistributable builds of Python

fork in 21 hours

issue commentvadimcn/vscode-lldb

Error launching terminal agent on Windows

To get rid of error messages when using PowerShell as a terminal shell in VSCode, you can set "lldb.terminalPromptClear" : null in user/workspace settings. Of course, this disables protection from junk input in the terminal (see above). Tradeoffs...

tyler274

comment created time in 2 days

issue commentvadimcn/vscode-lldb

Please merge the pretty printers from the LLDB project

Ok, I'll take a look. Last time I checked, rust-lldb's formatters did not implement synthetic children, and so were not suitable for display in VSCode's variables treeview.

brmmm3

comment created time in 6 days

issue commentvadimcn/vscode-lldb

Please merge the pretty printers from the LLDB project

Hi, Could you please be more specific, which formatters are you talking about? Which language and which type(s)?

CodeLLDB installs all the standard formatters that LLDB has, and then adds Rust formatters on top of that. Unless something new had been added in LLDB since v10.0.0, there should be no difference between the two for C++ datatypes.

brmmm3

comment created time in 6 days

push eventvadimcn/build-tools

push time in 9 days

create barnchvadimcn/build-tools

branch : windows-msys

created branch time in 9 days

push eventvadimcn/build-tools

Vadim Chugunov

commit sha 1275b1f22307797eaa69342849fc12aba611ffda

msys2 /tmp

view details

push time in 9 days

push eventvadimcn/build-tools

Vadim Chugunov

commit sha 67e694a17f81d468ff02d31d7f232db30a0e7348

ninja 1.10.1, zip 3.0, unzip 6.0

view details

Vadim Chugunov

commit sha 073156a0ac1d4b9c3b844e075c8ae1bc98bf2e67

Msys2 20200903

view details

Vadim Chugunov

commit sha 2ea48062cb2feac6058ba577ee0cbd1d21f3995b

msys2 automake autoconf

view details

Vadim Chugunov

commit sha b780c5d7491ac2deb2c3a8b3cf8914e2101070f7

msys2 pcre-devel

view details

Vadim Chugunov

commit sha 4d4c414aca5cd7a0b31dcede136d202b26a766f5

msys2 bison

view details

push time in 9 days

issue openedMicrosoftDocs/azure-devops-docs

The documentation of Artifact commands is unclear/incorrect.

  • For ##vso[artifact.associate]:
    • What is the purpose of each artifact type?
    • What is the difference between container and filepath artifact types?
  • For ##vso[artifact.upload]:
    • The purpose of containerfolder parameter is unclear.
    • The first code example shows the command without any parameters, but in reality artifactname seems to be required, whereas containerfolder is not - in contradiction to what parameter documentation says.
    • Can it be emitted multiple times to several multiple files to the same artifact? (Seems like yes?)
    • Can it be used to specify the relative file path within the artifact? (Again, seems that it can - by appending relative path after containerfolder, however in combination with multiple uses, it produces an error that the specified artifact already exists. Would be good to clarify how this was designed to be used.)

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

created time in 10 days

delete branch vadimcn/build-tools

delete branch : macos

delete time in 13 days

delete branch vadimcn/build-tools

delete branch : Linux

delete time in 13 days

delete branch vadimcn/build-tools

delete branch : Darwin

delete time in 13 days

create barnchvadimcn/build-tools

branch : darwin

created branch time in 13 days

create barnchvadimcn/build-tools

branch : Darwin

created branch time in 13 days

create barnchvadimcn/build-tools

branch : Linux

created branch time in 13 days

create barnchvadimcn/build-tools

branch : windows

created branch time in 13 days

delete branch vadimcn/build-tools

delete branch : windows

delete time in 13 days

delete branch vadimcn/build-tools

delete branch : master

delete time in 13 days

create barnchvadimcn/build-tools

branch : windows

created branch time in 13 days

create barnchvadimcn/build-tools

branch : macos

created branch time in 13 days

create barnchvadimcn/build-tools

branch : linux

created branch time in 13 days

create barnchvadimcn/build-tools

branch : master

created branch time in 13 days

created repositoryvadimcn/build-tools

created time in 13 days

created tagvadimcn/vscode-lldb

tagv1.6.0-dev+200901.0353

A native debugger extension for VSCode based on LLDB

created time in 23 days

delete tag vadimcn/vscode-lldb

delete tag : v1.6.0-pre

delete time in 24 days

issue commentvadimcn/vscode-lldb

Debugger works for a minute or two and then crashes

The last entry in the debug log is evaluation on hover, so I assume this is where it crashed. LLDB is not bug-free, unfortunately. :(

alexbaucom17

comment created time in a month

issue commentvadimcn/vscode-lldb

Can I remotely debug Android C/C++ code

I haven't personally tried that, but I don't see why not. Here are some resources to get you started:

  • https://github.com/vadimcn/vscode-lldb/blob/master/MANUAL.md#remote-debugging
  • https://lldb.llvm.org/use/remote.html
  • https://www.sh-zam.com/2019/05/debugging-krita-on-android.html
chenls

comment created time in a month

issue commentvadimcn/vscode-lldb

Breakpoints suddenly stopped working

Please see this. Most likely this is a problem with the debug info and/or source file path mappings.

jelling

comment created time in a month

issue closedvadimcn/vscode-lldb

Change lldb.libpython to use python 2

Hi, trying to change python lldb.lybpython to python 2.7:

"C_Cpp.errorSquiggles": "Disabled",
"cmake.configureOnOpen": true,
"lldb.library": "/Users/shlimov/Work/xcode_installs/xcode_Azul18A298_GlacierDogfood12A5121t/Xcode.app/Contents/Developer/usr/bin/lldb",
"lldb.libpython": "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib",
"lldb.verboseLogging": true,

getting the following issue when running: configuration: { type: 'lldb', name: 'Attach to Name (wait)', request: 'launch', custom: true, relativePathBase: '/Users/shlimov/git/leda/modem' } liblldb: /Users/shlimov/Work/xcode_installs/xcode_Azul18A298_GlacierDogfood12A5121t/Xcode.app/Contents/Developer/usr/bin/lldb libpython: null environment: {} params: {} [2020-08-16T09:16:03Z INFO codelldb::find_python] Query returned ["/AppleInternal/Library/Frameworks/Python.framework/Versions/3.7/Python3", "/AppleInternal/Library/Frameworks/Python.framework/Versions/3.7/Python", "/AppleInternal/Library/Frameworks/Python.framework/Versions/3.7/Python", "Python.framework/Versions/3.7/Python"] [2020-08-16T09:16:03Z INFO codelldb::find_python] Probing "/AppleInternal/Library/Frameworks/Python.framework/Versions/3.7/Python3" [2020-08-16T09:16:03Z ERROR codelldb::find_python] "dlopen(/AppleInternal/Library/Frameworks/Python.framework/Versions/3.7/Python3, 9): image not found" [2020-08-16T09:16:03Z INFO codelldb::find_python] Probing "/AppleInternal/Library/Frameworks/Python.framework/Versions/3.7/Python" [2020-08-16T09:16:03Z INFO codelldb::find_python] Py_GetVersion returned "3.7.3 (default, Jul 5 2020, 04:26:16) \n[Clang 11.0.3 (clang-1103.0.29.21) (-macos10.15-objc-selector-opts)]" [2020-08-16T09:16:03Z INFO codelldb::find_python] Parsed version as 3.7 [2020-08-16T09:16:03Z INFO codelldb::find_python] Accepted Listening on port 58057 [2020-08-16T09:16:03Z DEBUG codelldb] New debug session Could not find platform independent libraries <prefix> Could not find platform dependent libraries <exec_prefix> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>] Python path configuration: PYTHONHOME = (not set) PYTHONPATH = ':/Library/Python/2.7/site-packages:/Users/shlimov/git/hdc_wsoc_fw_shared_tools:/Users/shlimov/git/bennu/hdc_wsoc_fw_bennu_scripts' program name = 'python3' isolated = 0 environment = 1 user site = 1 import site = 1 sys._base_executable = '/Users/shlimov/.vscode-insiders/extensions/vadimcn.vscode-lldb-1.5.3/adapter/codelldb' sys.base_prefix = '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8' sys.base_exec_prefix = '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8' sys.executable = '/Users/shlimov/.vscode-insiders/extensions/vadimcn.vscode-lldb-1.5.3/adapter/codelldb' sys.prefix = '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8' sys.exec_prefix = '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8' sys.path = [ '', '/Library/Python/2.7/site-packages', '/Users/shlimov/git/hdc_wsoc_fw_shared_tools', '/Users/shlimov/git/bennu/hdc_wsoc_fw_bennu_scripts', '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/lib/python38.zip', '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8', '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/lib/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings'

Current thread 0x0000000119befdc0 (most recent call first): <no Python frame> Debug adapter exit code=1, signal=null.

how can I change the default python for the extension to be 2.7 and not 3?

closed time in a month

kurtikaaa

created tagvadimcn/vscode-lldb

tagv1.6.0-pre

A native debugger extension for VSCode based on LLDB

created time in a month

issue commentvadimcn/vscode-lldb

Connection refused

Huh, that's not supposed to be possible... At the very least, there should have been a connection codelldb has accepted from VSCode in order to start the debug session. Would you mind attaching a full verbose log?

Kovenas

comment created time in a month

issue commentvadimcn/vscode-lldb

[Feature Request] Add preference to allow using the system LLDB on macOS

What happens if you just add "lldb.adapterEnv": { "LLDB_DEBUGSERVER_PATH": "<system debugserver path>" } is workspace configuration?

alexfusco5

comment created time in a month

issue commentvadimcn/vscode-lldb

Connection refused

Just to be clear, "Before the message" refers to the period between when you start the debug session and when the "Failed to redirect stdio to a terminal." message appears? There should be about 5 seconds between these events.

Kovenas

comment created time in a month

issue commentvadimcn/vscode-lldb

Erratic step through simple code.

Which debug info format does clang use in this case, DWARF or PDB?
Also, please make sure you are compiling without optimizations.

AdrianJMartin

comment created time in a month

issue commentvadimcn/vscode-lldb

Connection refused

Does it show anything at all (without grep)? What about after the error appears?

Kovenas

comment created time in a month

issue closedvadimcn/vscode-lldb

One package deployment if the rust component ship as wasm?

Maybe this is a little early, but if the rust component could compile to wasm then we could ship that with the extension making it much easier to work behind corporate fire walls that only allow vscode extensions through.

Maybe this would need to depend on a wasi extension?

It’s quite possible we cannot do this yet, but this is definitely where we should be going - I’m sure the wasi team would be keen on trying to make this happen as vscode wasi extensions would be a great combination.

closed time in a month

gilescope

issue commentvadimcn/vscode-lldb

display template types and values on hover

Sorry, LLDB does not provide this sort of info.

dimas1185

comment created time in a month

issue commentvadimcn/vscode-lldb

Debugger does not start

Please try setting "lldb.terminalPromptClear": null in VSCode user settings (or change VSCode terminal shell to cmd)

human-0

comment created time in a month

issue commentvadimcn/vscode-lldb

Debug Swift

Can you please try removing lldb.libpython from your configuration settings?

lokinfey

comment created time in a month

issue commentvadimcn/vscode-lldb

Connection refused

Hmm, no idea. Can you please check which TCP ports codelldb is listening on? lsof -iTCP | grep codelldb
You'll need to do this in the first 5 seconds after launch, before the "Failed to redirect stdio to a terminal." message appears.

Kovenas

comment created time in a month

issue commentvadimcn/vscode-lldb

Unable to Debug Rust on Windows

Hmm, 3221225620 = 0xC0000094 = STATUS_INTEGER_DIVIDE_BY_ZERO. Is there anything unusual about your setup / debug launch configuration that might have triggered division by zero somewhere?
I am afraid I will not be able to investigate this without a repro case.

jfro

comment created time in a month

issue commentvadimcn/vscode-lldb

Change lldb.libpython to use python 2

Sorry, you cannot use Python 2.
Python 2 and 3 are not compatible at the binary interface level, you have to choose one or the other when compiling LLDB. Given that Python 2 is out of support as of 1/1/2020, it makes little sense to choose it over Python 3.

kurtikaaa

comment created time in a month

issue commentvadimcn/vscode-lldb

[Feature] Allow Catching Rust Panics Even When Not Using Cargo Integration

You need to set sourceLanguages=["rust"], otherwise, how'd codelldb know you are debugging a Rust program?

zicklag

comment created time in a month

issue commentvadimcn/vscode-lldb

Evaluate lldb expression using customRequest in another extension

Please see the Expressions section of the manual. In order to call C++ methods you'll need to use the native evaluator.

eddyc

comment created time in a month

issue closedvadimcn/vscode-lldb

Submodule `schemafy@18233a4` broken

Clone failed: git clone --recursive https://github.com/vadimcn/vscode-lldb.git

fatal: remote error: upload-pack: not our ref 18233a45f690d7331d5abecb4b06b243f85a4420
fatal: the remote end hung up unexpectedly
Fetched in submodule path 'adapter/deps/schemafy', but it did not contain 18233a45f690d7331d5abecb4b06b243f85a4420. Direct fetching of that commit failed.

closed time in a month

oxalica

issue commentvadimcn/vscode-lldb

Submodule `schemafy@18233a4` broken

Sorry, I needed to re-create the repo and did not re-push custom tags. Should work now.

oxalica

comment created time in a month

created tagvadimcn/schemafy

tagcodelldb-v1.5.3

Crate for generating rust types from a json schema

created time in a month

PR opened Marwes/schemafy

Add #[skip_serializing_if="Option::is_none"] to optional attributes.

Fixes #17.

+2 -1

0 comment

1 changed file

pr created time in a month

create barnchvadimcn/schemafy

branch : option

created branch time in a month

fork vadimcn/schemafy

Crate for generating rust types from a json schema

fork in a month

fork vadimcn/schemafy-1

Crate for generating rust types from a json schema

fork in a month

issue commentvadimcn/vscode-lldb

Evaluate lldb expression using customRequest in another extension

To get a stack trace, you need to specify the thread you are getting a stack trace of...  But for that, you'll need to know which thread is currently selected in the UI (assuming the process is in a stopped state in the first place).    I don't think VSCode currently exposes any API to query that.   Best you can do, is to listen for debug session events and record the last stopped thread id the way Debug Visualizer extension does it.

But I wonder if there's an easier way to do it...  Can you use stop hooks instead? E.g target stop-hook add -o 'e myvar.send("name")'

eddyc

comment created time in a month

push eventvadimcn/schemafy

Markus Westerlind

commit sha b76e10a12e6cc9a720161af9aec6cedfb66bac3e

Improve publish.sh

view details

Markus Westerlind

commit sha 533971ebad4da42f041983aa3ef15f50ac4c9e5f

bump version

view details

Markus Westerlind

commit sha e8dfb9739a41840ad39fcbf9031b04adf35d7c94

(cargo-release) version 0.4.5

view details

Ryan Roberts

commit sha fae0f67a7dc3632c43102410109ab0cbd6a45161

Fix: All current and reserved keywords

view details

Markus Westerlind

commit sha 4eb49a3387866c965ba08679007ddf3bf8d4b1a5

feat: Use a procedural macro to generate the types

view details

Markus Westerlind

commit sha d1dce358b342972f335045bafd1eb4c9fe41e5f5

feat: Remove the snapshot crate and rely on manual updating of the schema

view details

Markus Westerlind

commit sha c32ba74a256fa694e0ee66d79e7314ca33921149

doc: Link to docs

view details

Markus Westerlind

commit sha 4db5071aaea5a24d3eb9e6554504b460d8f8d131

cargo fix --edition

view details

Markus Westerlind

commit sha 0c4785be438a54931d580fe69d37cabaf2ab0e47

cargo fix --edition-idioms

view details

Markus Westerlind

commit sha b09242e1411754e9b571e69d1b1837f6690d463c

schemafy_core

view details

Markus Westerlind

commit sha b7cc437354065f4695afc769b1cd428fc1bc88b1

Don't regenerated the schema every time

view details

Markus Westerlind

commit sha 7821561bdcc0cfdc33574962bf450795eb43d140

Merge pull request #22 from Marwes/proc_macro feat: Use a procedural macro to generate the types

view details

Markus Westerlind

commit sha 9212de34f310f2a91a2790b05beae874bacab9d0

Merge branch 'master' into master

view details

Markus Westerlind

commit sha f96dad38513c899f383eb2f65e35abb5443dccbe

Update lib.rs

view details

Markus Westerlind

commit sha 939cb806546bfc9dd1998fdb015b25445ecd23fc

Merge pull request #21 from presciense/master Fix: All current and reserved keywords

view details

Markus Westerlind

commit sha 76c9c91724e9f34a2a823be484642152dc01dbec

Version 0.5.0

view details

Markus Westerlind

commit sha e41c207f8df8b7fedb136c87d361cf5286fa537e

Update Cargo.toml with links

view details

Markus Westerlind

commit sha 565b5e2c662a78ad6b7326449a968115d8803797

Fixed unused warning

view details

Anthony Deschamps

commit sha 61d8376ddc0b80e202fba4d74eac10c8541d5072

Add JSON Schema Test Suite submodule.

view details

Anthony Deschamps

commit sha e9d833c1a119f574ba0ab420dd427dd65c41a6f5

Add a binary target to generate tests from the test suite.

view details

push time in a month

issue commentvadimcn/vscode-lldb

vscode

thread 'main' has overflowed its stack Debug adapter exit code=3221225725, signal=null.

JRAndreassen

comment created time in a month

issue commentvadimcn/vscode-lldb

Conditional breakpoint expression syntax

Please see the Expressions section of the manual. Since it looks like you want to call a C++ method, you'll probably want to use native expressions, i.e. /nat set.size() == 3.

gkoulin

comment created time in a month

issue commentvadimcn/vscode-lldb

Unable to Debug Rust on Windows

If you want to use PS for shell, you can set "lldb.terminalPromptClear": null in VSCode user settings.

jfro

comment created time in 2 months

issue commentvadimcn/vscode-lldb

Debugger not hitting breakpoints when using DWARF 5

Not much I can do about that for now. Hopefully DWARF5 support will improve over time as I pick up newer LLDB versions.

Tachi107

comment created time in 2 months

issue closedvadimcn/vscode-lldb

std::set variable inspection is unredable

OS: macOS 10.14.6 VSCode version: 1.47.0-insider Extension version: v1.5.3 Toolchain version: clang version 10.0.0 Build target: Python version: Python 3.7.7

When inspecting std::set container variable, the output just shows underlying red-black tree structure. Screenshot 2020-07-09 at 10 18 58

Similarly some boost types like variant and optional also show internal raw data structures instead of human readable.

closed time in 2 months

gkoulin

issue commentvadimcn/vscode-lldb

std::set variable inspection is unredable

In order to decode data structures LLDB needs the appropriate data formatters. LLDB project provides them for some C++ types, but not all, and certainly not for boost. At the moment I have no plans for getting into adding new C++ formatters, sorry.

gkoulin

comment created time in 2 months

issue commentvadimcn/vscode-lldb

Debugging 32-bit C++ application

Would be nice to get more details about the OS, etc, as described in issue template.
But generally, yes, 32-bit code support in LLDB is not great at this point, especially on Windows. My extension merely wraps LLDB as VSCode extension, I can't do much about its core functionality.

vcouvert

comment created time in 2 months

issue commentvadimcn/vscode-lldb

feature request: add expression evaluation to watch window

You already can do that. Please review the expressions section of the manual; what you want in this case are the "native" expressions.

dimas1185

comment created time in 2 months

pull request commentvadimcn/vscode-lldb

Add breakpoint support for zig

Thanks!

rojuu

comment created time in 2 months

push eventvadimcn/vscode-lldb

Roni Juppi

commit sha 5bbf2ed08fcffd9a8c6696736ad788c91588fd29

Add breakpoint support for zig

view details

push time in 2 months

PR merged vadimcn/vscode-lldb

Add breakpoint support for zig

Awesome extension! Have been using this as debugger for C++ and zig. This change allows setting breakpoints also for zig language.

+3 -0

0 comment

1 changed file

rojuu

pr closed time in 2 months

issue commentvadimcn/vscode-lldb

Debugging child processes

@Trass3r: It isn't clear how this can be automated, let alone on all platforms (AFAIR, auto-attach only works on MacOS). This also goes beyond the scope of my project (which I see as integration of LLDB and VSCode, without adding core LLDB functionality).

Perhaps this can be achieved with scripting? When you only need to care about your specific environment, you can step into the body of fork(), read child process pid from a register, etc, and not have to worry that it's gonna look different in next version of libc.

TheAifam5

comment created time in 2 months

issue commentvadimcn/vscode-lldb

System environment variables

uses vscode-lldb for debugging

Are you sure about that? The installation instructions for nvim-dap point to lldb-vscode, which is a confusingly similarly named DAP adapter provided by the lldb project.

Shatur95

comment created time in 2 months

issue commentvadimcn/vscode-lldb

One package deployment if the rust component ship as wasm?

Even if Rust code could be compiled to wasm, what about liblldb? It uses a bunch of deeply platform-specific APIs, like ptrace. I doubt wasi has any plans to support those.

gilescope

comment created time in 3 months

issue openedmicrosoft/vscode

[Debug] Debug console completions don't work the way they are descripbed in DAP specification.

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->

  • VSCode Version: 1.46.1
  • OS Version: Ubuntu 20.04

(This is in the context of implementing "completions" request in a debugger extension)

Steps to Reproduce:

  1. Debug session starts.
  2. User types "se" in the debug console. VSCode sends a completion request to the debug adapter: "arguments":{"frameId":1001,"text":"se","column":3,"line":1} (I'm copying only the relevant parts of the messages here).
  3. The adapter responds with body":{"targets":[{"label":"ttings","length":0,"start":3}]} (I also tried just "body":{"targets":[{"label":"ttings"}]})
  4. Nothing happens. If I force suggestions with Ctrl+Space, VSCode says "No suggestions."

According to my reading of DAP spec, this response should have caused "ttings" to be inserted at the current cursor position. In reality, it seems that in order for completions to appear, the completion text must start with the current word under the cursor, i.e. "body":{"targets":[{"label":"settings"}]}. As far as I can tell, the "start" and the "length" attributes are completely ignored.

created time in 3 months

PR closed vadimcn/vscode-lldb

Update value.py for python3 support

When using vscode-lldb for debugging rust, I attempted to access a slice of a vector from the debug console:

buffer[0:100]

It returned name 'xrange' is not defined

Looking in value.py I found that there's a reference to xrange, which isn't valid in python3. This similar fix exists (but other way around) here: https://github.com/vadimcn/vscode-lldb/blob/35151d7d2de84376987e2bbc747192034e307584/formatters/rust.py#L10

This can be reproduced by entering a debugging state and trying to access a valid slice of a vector/array-like collection.

I'm all ears on how you'd like me to enhance this PR to make it acceptable.

+3 -0

1 comment

1 changed file

ablakey

pr closed time in 3 months

pull request commentvadimcn/vscode-lldb

Update value.py for python3 support

Since Python 2 is dead now, I think I'll just replace xrange with range. It'll still work in Python 2, would just use a bit more memory.

ablakey

comment created time in 3 months

PR closed vadimcn/vscode-lldb

Prepend the type name to the container summary.

For your consideration: adds a little bit of additional information to the thing that VSCode displays to users.

Before:

image

After:

image

(Notice that in the latter case you don't even know what variant of the enum it is #enum

+1 -1

1 comment

1 changed file

samscott89

pr closed time in 3 months

issue commentvadimcn/vscode-lldb

codelldb::dap_codec debug Process exited with code -1

Can you please try to follow these troubleshooting steps?

liuxiaozhe

comment created time in 3 months

issue commentvadimcn/vscode-lldb

There are some error messages when debugging in windows, but it can run debug correctly

Please add them (one at a time) in user or workspace configuration.

haozia816

comment created time in 3 months

issue commentvadimcn/vscode-lldb

There are some error messages when debugging in windows, but it can run debug correctly

Does adding either of these settings help? "lldb.terminalPromptClear": [""] or "lldb.terminalPromptClear": null

haozia816

comment created time in 3 months

more