I went through the entire app and two Google pages and didn't found it. How can I enable the output window?
If you are referring to build output: As of the latest EAP, you can enable this via:
Preferences -> Build, Execution, Deployment -> Toolset and Build -> Write log to output
It is disabled by default as of the time of this writing.
Currently the build output window available only for not incremental build. We try to add it in next EAP build.
For anyone looking for the "Debug window", it's on View->Tools Windows->Debug and change the mode to "Debugger Output (LLDB)" https://www.jetbrains.com/help/rider/Debug_Tool_Window.html
Related
For an external library I need to build and run it on x64 configuration.
It seems to do this on every project despite the setting in the publish window. It does seem to honor the Release/Debug setting, but not the Platform setting.
How to proceed?
It seems to do this on every project despite the setting in the
publish window.
The Any CPU won't change because It's a default platform(Like a name), and the any settings actually are changed. That's why your Debug Output always shows "Debug:Any CPU".
This setting could be change,
Build->Configuration Manager->Project Platform->New
After these you go back to your Project Properties ->Build and click Platform x64 will be there. You could also switch them here.
Hope this could help you, if you still have other questions, please let me know.
I am very new to environment of Android-Studio and after enabling "Run in background" while downloading a plug-in, I don't know how to restore that default pop-up window showing status of downloading plug-in.
Please give step by step way to get it back.
You can go in menu "Window -> Background Tasks -> Show".
I hope your download is complete by this time. ;)
Close the SDK list window using 'Cancel'. Now you will be able to see "Events" just left of "Configure". Click on it to see currently running installations.
Hope it helps!
I installed Reaction-Commerce on a Ubuntu (Trusty).
Now I would like to debug/customize the project. For this purpose I installed Atom since it was mentioned on the project site.
How can I hook a debugger to the running "reaction" project?
What Atom package do I need?
It's not Atom, but VSCode is similar. Here's how I was able to setup debugging:
Create new reaction project from Terminal
mkdir test
cd test
reaction init
cd reaction
Open vs code from Terminal (must be in the reaction dir) code .
Click on debugging (there should be ‘No Configurations’ in the drop-down)
Click the gear icon to create a new Node.js configuration
Edit launch.json:
configurations.program -> “${workspaceoot}/server/main.js”
Save the file
Navigate to /server/main.js
add debugger; before Startup();
Save the file
Open Integrated Terminal (View | Integrated Terminal)
Type: reaction debug [it will start the app and eventually pause at the debugger statement]
Once it says that it’s paused, switch to the debug view in the left nav and select "Attach to Process" from the dropdown.
Then press the ‘start’ button (and select the Node.js process)
You should see the execution paused on the debugger statement entered in Step 12.
At this point you can step in, out, or over code statements.
I have not found a good simple tutorial for this. I just want the app to freeze at the breakpoints so I can explore the contents of the various variables, particularly their json content.
This is a garbage documentation:
http://www.jetbrains.com/webstorm/webhelp/running-and-debugging-node-js.html#d40161e701
I can't even set up breakpoints. Is it so simple to do this in Eclipse...
UPDATE
Using Webstorm 7.0's early access build, the debugger works flawlessly. I just made a new project, added a breakpoint and used Debug. Stopped at that breakpoint with no problems whatsoever, so apparently Webstorm 6.0's debugger sucks :D
You can get it here: http://confluence.jetbrains.com/display/WI/WebStorm+7+EAP Beware, it expires on 8 August.
I use webstorm and it's great. Having looked at that documentation, I agree. If you're just starting out, you don't need all the remote and attach to existing processes options.
The easiest option would be to rightclick on your main js file and choose debug. Setting breakpoints is the same as in most editors these days, just click left of the line.
If you don't get the debug option when you right click then you need to make a run/debug configuration which sounds worse than it is.
Select "Run" -> "Edit configurations".
Click the plus sign.
Choose "Node.js"
Click on the browse ... button on the Path to Node App js file and choose the file you want to debug
Click Ok.
Click on the bug!
I am trying to debug Node.js (v0.6.1) with Google's Eclipse debugger plugin for V8. I'm using Eclipse v4.1.0 on Windows7. I followed the Using Eclipse as Node Applications Debugger, but whenever I try to attach to a running Node.js (port 5858) process, I get a pop-up error message saying:
An internal error occurred during: "Debug session initialization: Node-5858".
Exception occured in callback
Any suggestions ?
I have been looking into a problem similar to this, this is what I have found
The instructions for setting it up, might just be worth re-reading these to make sure everything is as it should be:
https://github.com/joyent/node/wiki/Using-Eclipse-as-Node-Applications-Debugger
Do note that when looking around at a similar problem i located this help ticket on google code, it relates to a number of users who are having problems with Node.js on windows:
http://code.google.com/p/chromedevtools/issues/detail?id=53
It might be worth just downloading the newest version of Node.js as I believe this now has the fix in place, else download the fix file then mention within the ticket.
You can try to test for Nodeclipse version 0.2.0 beta.
http://www.tomotaro1065.com/nodeclipse/
GENERATING OF EXPRESS PROJECT
Select the [File]-[New]-[Project] menu.
Select [Node]-[Express Project], and push [Next] button.
Enter [Project name], and push [Finish] button.
DEBUGGING
Open the JavaScript source files that you want to set breakpoints.
Double-click on the ruler at the left end of the line you want to set a breakpoint.
If you want to remove a breakpoint, double-click on the ruler again.
Select the main source file of Node Application on the Project Explorer, open the context menu by right-clicking, select the [Debug As]-[Node Application] menu.
Just try this :
After creating the project, go to the cmd and provide the filepath of the file which you want to debug.
Now run the command node --debug-brk demo_node.js
(where demo_node.js is filename)
Now come to eclipse side, open the same file and set the break points.
Right click on the source file and select [Debug As]-[Node Application].