I am using webstorm 7.x and google chrome + the IDE chrome debbuging plugin.
I am able to debug my unit test.
When I have set a break on a certain line of code I would like to open a window where I can execute code.
How can I do this in webstorm?
You can use 'Evaluate expression' (Alt+F8) for this.
We plan to make debugger console interactive in the next WebStorm version - please vote for WEB-1171 to be notified on any progress
Related
Summary: debugger ignores breakpoints on Appceleration Titanium Studio IDE.
I'm using Appcelerator Studio, build: 4.10.0.201709271713, fresh install on macOS 10.14.1 (Mojave). My iOS project compiles and runs on the simulator just fine, everything behaves properly normally.
When I try and debug, however, execution ignores any breakpoints and just barrels on. I've checked all obvious settings, tried setting breakpoints every way possible, no luck.
If I launch the app under debug in the simulator and just let it sit there, eventually a dialog box will pop up saying "'iOS debugger on simulator...' has encountered a problem. Debugger failed to connect".
Anyone out there know what to do from here? I've been using Studio for years and the debugger part has always 'just worked'. I'm not sure where to look for port and connection settings.
I just upgraded to Xcode 6.3 and I have lost the unit test status/run indicators that were displayed in the left gutter of the editor. The status/run indicators don't immediately show in the Test Navigator either until after I perform a compile and test (Ctrl-U). After the tests have run the Test Navigator will display the status/run indicators but the status/run indicators in the editor are never displayed.
Has anyone else noticed this? I would really need to get these back. I hope someone knows how to fix this.
Thanks in advance.
Sorry. I thought I'd read through the Apple's latest release notes for Xcode, but I apparently missed this part. Thanks anyway.
Swift tests are not automatically discovered in this release of Xcode.
Test annotations in the source editor sidebar will not appear, and the
test navigator and the table of tests in the Test action of the scheme
sheet will be empty. You can run Swift tests by selecting Product >
Test. Once tests have been run, they appear in the test navigator and
the scheme sheet. The following limitations apply:
Tests discovered through execution in this manner provide limited
interaction in the test navigator. For example, Run buttons do not
appear and clicking on a test in the navigator does not jump to the
source code except in the case of a test error. Run buttons and test
success/fail indicators will not appear in the source editor.
(20373533)
This bug in XCode 6.3 is fixed in XCode 6.3.1.
Gerd
When a test hangs in a loop, the small green progress bar in the test runner does not proceed, but there is no way to stop the test run. Or is there?
VS 2013
Edit: This occured when using the XUnit TestRunner. The Cancel button simply did not show up. After testing various test runners in a new solution, it turned out, that it works with all of them. Finally it also worked with my original solution. So there was some anomaly in the state of my VS environment that caused cancel to disapper.
You can click "Cancel" in Test Explorer:
Show Test Explorer by going to TEST > Windows > Test Explorer.
This is in Visual Studio 2013.
Instructions for other versions of VS can be found here
Sorry for waking up an old thread:)
just wanted to share my solution here, I had the same issue on VS 2015.
There is some text below the search input just where the cancel should appear (take a look at #Codeman print screen), the text is actually some description on how you can setup a build for your tests, the text is several lines and at the end you have "do not show this any more" just press it and then the cancel button appears:)
Very strange bug, sorry I do not have some print screens of this
hope it helps someone
VS2015. If the hanging tests are executables instead of DLLs you need to kill those tests in the task manager. You need to close the Test Explorer Window to prevent automatic running. While the tests are running/hanging you will not be able to compile the according project.
For me the solution was to go to Task Manager, locate chromedriver and end the task.
Visual Studio 2022 Professional version 17.2.3.
I have found the solution to this issue. To stop the run after cancel is pressed, just set the 'Terminate process on cancel' option to True.
I am using Xamarin Studio as a D environment. I followed all the instructions given here, and the environment works OK. However, whenever I click the 'play' button in the corner, which is meant to build and run my project, regardless of which settings I give it, I can't get it to run. More specifically, the build succeeds, but then I get an error (which I also can't seem to read the entirety of), which starts with
"Cannot execute [name of my project]. The type initializer for 'MonoDevelop.Debugger.Gdb.D.ToStringExaminatio..."
I've tried searching for answers to this, but have found none. Any and all help would be greatly appreciated.
With Xamarin Studio 4.1.7 on OSX, Mono 3.2.0 and Mono-D 0.5.3.7 and debugger adding 0.2.2, I can start the applications using 'Run without debugging' in the 'Run' menu.
I can't succeed in using the debugger, but I think is an OSX problem: should work on linux.
I'm trying to debug shell extension (IContextMenu) in Windows 7 with Visual C++ 2008. I have set DesktopProcess=1 in the registry and set host app to explorer.exe. But when I start the debugger, it launches explorer.exe and then detaches from the process. DllMain of the shell extension isn't called.
The same code with exactly the same settings launched in debugger without any problems in Windows XP + Visual C++ 2008.
Any thoughts how to debug the shell extension in Win7?
I've found a nice workflow that I think is the fastest way to rapidly iterate the code-build-test cycle when developing shell extensions. The following should work on any Windows version.
First prepare - set the start program of your shell extension project to be c:\windows\explorer.exe and also set it to be the start-up project.
Then, whenever you want to debug your shell extension perform the following steps:
Click on the task bar and press Alt-F4 - this will bring up the shut down dialog
Press Ctrl-Alt-Shift-Escape - this combination will close explorer.
Use Alt-Tab to go back to Visual Studio and press F5 - explorer will now launch with the VS debugger attached to it from the very beginning.
When done, just stop the debugger session. This will kill the debugged instance of explorer and will also automatically start a normal instance of it. This will also unlock the shell extension DLL so that you can build it again.
Caveat on Vista and 7 - be sure to run the Visual Studio that you use for debugging in non-Administrator mode (non-elevated), so that the explorer is started in its usual non-elevated mode.
Try launching explorer and THEN attaching the debugger to it.
You could try putting a DebugBreak() call in your code. This should launch the just-in-time debugger at the call and give you an idea of what is going on.
You should take a look at gflags.exe, part of the standard debugging tools sdk. It's got all the options you need to configure (global)flags for any process startup/services/heap/pool-tagging/stacktrace's-on-allocation etc...
Debugging Explorer.exe is usually overkill for extensions that operate in a shell view.
I personally use a little app I made that hosts an instance of IExplorerBrowser similar to this example. If your IContextMenu item is not the default item then you can just use Notepad.exe and its open file dialog...