Configuring VS Code for debugging Rust - visual-studio-code

I have been through the official VS Code documentation section on Rust and I have the Rust Analyzer extension installed.
But I can't seem to see break points that I set in the code.
I see what appears to be assembler.
Is there another clear step by step guide to configuring VS Code to debug Rust programs?
I have been through the VS Code documentation on debugging Rust
I have installed the necessary extensions according to the documentation.
I can get a debug session to run.
Source code:
Running debug:

I tried setting a function breakpoint on main, and it does indeed show assembly. This is probably a limitation of lldb/rust/vscode, and not user error. If you set a breakpoint in the file, though, it does work:
If that workaround doesn't work for you, you'll probably be best finding/opening an issue on the CodeLLDB repo.

Related

Elixir: VS Code ExUnit cannot find Mix

I cannot load or run my tests, from within VS Code.
I'm a new user to Elixir, and to VS Code. I'm running Lubuntu 21.10 (Impish). I've downloaded Erlang/OTP 25 (.deb), and Elixir 1.14 (precompiled binary in /usr/share/elixir), and can get anything I need running in a Bash terminal. Again, in a standard QTerminal window,
erl, iex, mix, elixir, etc. all work fine.
In VS Code, however, I get some errors. I feel stupid, but I'm coming from Sublime Text, so please forgive me.
In the left pane of VS Code, ExUnit shows an error (red):
Clicking on this error gives me this, on the bottom right pane. The command line options, passed to mix test, seem to be the default configuration:
This result is bizarre to me, because I can open the integrated terminal, execute /bin/sh, and then run the exact mix test line that's displayed:
/usr/share/elixir/bin has been added to my PATH variable, in ~/.bashrc, ~/.profile, and /etc/environment.
However, I am further confused by all tests being excluded, and wonder if there's some connection to the core issue:
Note that I can run my tests just fine, using different command line options. I've tried adding tags, but that didn't fix the problem.
I tried Google'ing this, and played around with my settings. Here is what I have configured in the "User" settings.json, and I made sure nothing overrides this in "Workspace" settings:
Changing the useNativeTesting setting doesn't solve the problem.
On another (?) note, I get a "failed to run elixir" upon VS Code startup:
Again, I have no problem running commands from a Linux terminal, or from a terminal within VS Code.
Plot twist: If I remove the precompiled Elixir 1.14, and downgrade to an older version, via apt, the problem goes away. But Lubuntu 21.10 doesn't offer Elixir 1.14, and I'm really into using the new dbg() feature.
But for now, I cannot load or run my tests, from within VS Code, apparently because Mix cannot be found.
Thanks to Daniel Imms, from the VS Code team, for answering my question on Twitter:
"Try moving where ever you init mix and elixir (.bashrc?) into your .bash_profile and then logging out and in again or restarting. I'm guessing it's in your bashrc which doesn't run in non-interactive sessions like in tasks."

SuiteScript with Intellisense in VS Code

I have the latest Visual Studio Code.
I have installed the latest SuiteCloud Extension for VS Code.
There is no intellisense.
I have also installed the SuiteNippets extension -- which is ok--but not full intellisense.
I am baffled as to why this is missing. Do I need to import/reference something from NetSuite--despite using their extension already?
How do I enable intellisense in VS Code for SuiteScript?
See my previous answer to a similar question. It's possible to use the Head-in-the-Cloud bundle to create javascript transpiled from TypeScript files. The code completion is good and you have the added benefit of type checking.

Rust/VSCode Debugging Does not Display Peripheral Registers

I am failing at getting the peripheral registers to show up on the vscode debugging screen.
Using a Nucleo 144 board, I downloaded the appropriate STM32H743.svd file and put in the path in launch.json as "svdFile": "${workspaceRoot}/STM32H743.svd" like instructed at cortex-m quickstart guide.
Everything else about the debugging works alright except this. There is no obvious error message anywhere. I am using the rust-analyzer and Cortex-Debug extensions.
This is what i see in the VScode debugging tab:
I have come across this discussion, suggesting that one should use the pre-release version of the Cortex-Debug extension for now. This has indeed fixed the issue for me.

Why do no programs run in visual studio code?

I recently got a new computer and reinstalled visual studio code but I haven't been able to run any of my files. The error has occurred with both python and C++, so I feel as though it is the IDE that is the problem. I have looked online and there are no straight answers as I have tried following some solutions which have resulted in different errors.
The error above comes up when I run (F5) a simple line of code in c++. Does anyone have a solution?
Thanks, Jacob
[EDIT]
For my python files to work I have to manually select 'Python: current file' but for c++ files they still have the same error.
First step, uninstall python from this machine.
Second, reinstall and make sure that you check the box "add to path".
It's pretty easy to miss as it's a small box, and I missed it my first time installing python earlier in the year. Here's the box you may have missed while installing.
It could be your extensions.
I had a similar error message and simply updated all of my extensions and then my SDK. I was then able to run my code within the IDE. I was using VSCode for c++ and also updated my GCC compiler along with the extensions.
Also look into your computer's environment variables, if you have changed the %PATH variables it may be affecting your ability to run/compile programs.

Input does not work in Visual Studio Code

So I just started learning programming and I think something is messed up with my code runner in Visual Studio Code. When I try to use input in Python I can not write anything in the terminal. This problem came out recently. It writes that when I try to input anything that it "cannot edit in read-only editor". I also checked in here what could be the solution, but it did not help. Input still does not work. I am on Linux, and I also tried to uninstall the program and code runner as well, none of them worked so far.
Ps: I tried the Code-runner: Run in Terminal box check method, which did not work at all.