I can't find where to view the machine code anywhere from googling (the solutions I tried were either outdated or didn't work: it's not listed under Window or going through Debugging for me). I'm supposed to look at it and compare it to the source code that generated it for an assignment. I'm fine with using another ide or something else besides netbeans, I just need to see machine code based on my source code.
Related
(Currently using VS Code on macOS Monterey, mostly for React and JavaScript.)
When I used to import a component at the top of my file, Vs Code would suggest the path of the file. I would simply press enter or click on the suggestion and VS Code would fill in the rest. Seems to me like a standard feature of VS Code, and I've grown pretty accustomed to it.
Now, it doesn't suggest anything. I'll type out a file that exists in the project, and nothing appears. I've tried it with several projects, and none of them suggest anything anymore — when just last week it was working fine.
trying to import
One thing... I have a lingering suspicion that it's from doing this:
npm i #types/react -g
A friend recommended I add it. With it, you can declare a component in your project and VS Code will auto import it. Really, it's the only thing I can remember changing since this strange behavior with VS Code started, but I'm not positive. Just a suspicion. I've tried to remove it, but it didn't fix anything.
I've done a bunch of stuff found on stackoverflow already with no improvements:
adding to setting.json, like this, or this
even deleted VS Code w/ extensions
I am trying to set up vs code currently to work with my a-star 3.3V module. I have code already working that I have uploaded successfully on the Arduino IDE, but I run into an error (see below). I have done some googling and wasn’t able to find a solution that worked, as most of them involved ensuring the board and ports were configured correctly, but I have already done that (to the best of my knowledge).
[Error] Uploading sketch ‘tuya-a-star.ino’: Exit with code=1
I have included some of the different things below so you can see what I mean, I am hoping I have missed something small here. The correct board and version is also selected as is the correct port. I have also selected the Arduino type for the C/C++ configuration.
arduino.json file
{
“configuration”: “version=8mhz”,
“board”: “pololu-a-star:avr:a-star328PB”,
“output”: “…/ArduinoOutput”,
“programmer”: “pololu-a-star:stk500for328PB”,
“sketch”: “tuya-a-star.ino”,
“port”: “COM4”
}
I am working on a c++ project using a version of eclipse (Atollic TRUE studio) and this morning my indexer was working just fine. Currently, almost everything is broken (some local things within a file still work, but the rest fails). Googling around told me to do a indexer->rebuild. I have done this is the passed as well and back then it worked just fine. I noticed that, during the indexer rebuild, some progress bar was shown. Now, if I execute the indexer rebuild, nothing happens and I don't see this progress bar anymore. I have not changed any project/workspace/indexer settings, at least not on purpose anyway.
Among others I found this post
Eclipse indexing not working
where BЈовић claims
If this doesn't work, then you are out of luck. c++ is very difficult language to parse.
Is this really the answer? Or is there some smart trick that I missed?
I'm using the "SPIDER" IDE for SICSTUS Prolog development, as instructed by the SICSTUS Manual and the documentation on the SPIDER IDE itself. When debugging, under the 'SICSTUS Debugging' perspective, the variables do not show on the Variables window, as can be seen in the top right in the image shown here (it's the first thing in the Spider page)
I set up everything according to this guide and this is, as far as I can tell, the only thing not working. Are there any additional steps to get the variable bindings while debugging?
Thanks in advance,
edit: I've recently reinstalled everything in the same system after formatting a drive, and it now works perfectly. I have no idea what, but I assume I did something wrong the first time.
Variable bindings should work by default. However, some variables may be omitted depending on compiler optimizations and other factors. Try it with the example program shown in the SPIDER image.
I am having a difficulty while attempting to debug some code in grails. It is difficult to put into text, so I have posted a screencast showing exactly what the problem is here. In short, while I am debugging the debugger starts jumping from place to place and not following the program logic I have in place. The only other similar question I have found is a year old, had no solution, and can be found here.
The best guess I have so far is that the debugger is displaying the text I have typed in, but is actually executing an older version of the class file which it has cached somewhere. Therefore, I tried:
cleaning the project
manually deleting all of the class files from the target folder and from the target-eclipse folder
Searching my entire hdd for additional files with similar names
removing my project from the workspace and re-adding it
closing and reopening the IDE
grails refresh-dependencies
Importing the project into a new IDE (I was using GGTS, I switched to IntelliJ)
None of those solutions had any effect. I realized that the issue was in a .groovy file, and I was writing almost pure Java, so I deleted the .groovy file, and re-created the class in a .java file. That solved my problem. Unfortunately I am having the problem again, and this time it is in a controller that heavily relies on the grails framework, so that solution is not an option. Other than also being in a .groovy file, another similarity is that the code breaks on an if statement.
My next steps:
Verify that the application is not executing the code I see by using print functions to monitor actual execution flow.
comment out the entire function and re-add functionality one line at a time to see if I can see what breaks it.
Delete the .groovy file, and re-create it as another .groovy file.
Any help is appreciated, and since I can't find any answers online I will continue to update this question as I learn more.
See my comment on the jira issue that you raised. You have found a problem with the groovy compiler and how it calculates line numbers. This is not a problem with executing the wrong class files or using a broken debugger. The debugger is doing exactly what it is expected to do. It is the compiler that is providing erroneous line number information.
The next step, as described in the issue, is to provide a simple project that recreates the bug. I tried to do so myself, but could not. So, please supply something that we can work with. Then we can notify the groovy compiler team.