In Mono Develop 3.X, there is a menu option to configure exceptions we wish to break on (Run -> Exceptions).
But with Mono Develop 5.7 IDE it is no longer there?
Also Debugger is not breaking on exceptions.
Any idea How to get it back, probably some add-ins ?
Exception catchpoints are now in same dialog as breakpoints.
You can open this dialog via
Run->New Exception Catchpoint
Breakpoints pad has button "New Exception Catchpoint"
What is nice about this is, you can use conditional and counting filters and different conditions/counts for different exceptions and also print debugging text(tracepoint) instead of breaking.
Most common use case is to add "System.Exception" and check "Include subclasses".
Related
The code I am currently working on is running into a problem that seems to only get fixed when I disable the Show Logical Structure button in Eclipse. However, I prefer to work in Intellij, is there an equivalent way to disable this in Intellij so I can continue working in this IDEA?
The option is called Enable alternative view for Collection classes, try disabling it:
I'm using IntelliJ IDEA 12. When I run "make project", "debug" or "run" task it does some compiling, shows little bubble that there are warnings, shows grayed-out tool window "message" and after few seconds it hides the nameplate of messages window.
Why is compile log missing? What to do to fix this? I'd like to see (in IDE) what causes those warnings...
PS: I'm not sure, but it might started doing this when I started using Scala (it's now a mixed Scala-Java project).
If you've previously selected "Hide Warnings" then the Messages window is unavailable if there are no compilation errors. It is not even possible to show the empty window using View->Tool Windows-> Message or Alt-0.
Solution:
introduce a compilation error
build, the Messages window should reappear to show your error (or at least be accessible via the View menu)
go to the Messages window and deselect Hide Warnings
fix the compilation error
Rebuild Project and all your warnings will be visible
(I had the same symptoms on 13.0.2 and this worked for me)
For me, it pops up on "Rebuild Project". Maybe that helps.
The window should be there any time IDEA compiles the code. (If there is a not a code change, and you rerun something there is no compiling done and the message window will not show). It is accessible (by default) via Alt+0 (Zero, not the letter 'Oh') or via View > Tools Windows > Messages
You may have a combination of some tool window settings causing this.
If all the tool window buttons are hidden, the messages tool window will be as well. You can toggle this setting via View > Tool Button or the icon in the very bottom left corner of the IDE. To temporarily show the buttons when hidden, hit the Alt twice, holding it down on the second hit.
If the messages tool window is not set to "Docked Mode" and "Pinned Mode" it will close after the compile.
If the above is not the issue, make sure you are using the latest version of IntelliJ IDEA, v12.1.6, and the latest version of the scala plug-in, v0.22.302 (Go to Settings > [IDE Settings] > Plugins and look for the scala plug-in). Those versions work as expected for me.
Looks like u do not have any errors and warnings! In this case in Idea "Messages" tool window auto disappears. I hade the same issue and passes half an hour to understand the reason!
How can I step back to a previous line when I'm debugging in IntelliJ?
I don't see anything in the debug menu or commands to do this.
There's no backward debugging support in IDEA currently. Nevertheless (for Java) there is Drop Frame action and button on the debugger toolbar. It lets you go one frame up in the stack and re-enter the current method.
The Chronon plugin, which is available for free with IntelliJ IDEA 13, can do this for you. It has limitations, though; chiefly, if your application runs outside of the IDE itself (like a Tomcat or Jetty server), the free version won't be usable with your setup.
I recently have encountered a weird issue with my project: as soon as I click debug and it builds the project, it stops debugging. There isn't any error message, or anything else that comes up, including the form itself.
I've tried messing with the settings: no splash screen and I've even changed the startup form to a blank Windows form. What could be causing this problem? Is it Visual Studio or my code?
Probably your program is exiting normally. Set a breakpoint at the first statement to be executed, press F5, then single-step through the program until you get to the last statement executed.
If the first statement is never reached, then one of two things probably happened:
You're mistaken about which statement is executed first, or
The program is terminating during initialization, probably because a class constructor is exiting the program either normally or abnormally.
A few ideas:
Use Debug->Exceptions, and check all the checkboxes so you break when an exception is thrown.
Use Debug->Step into to step into your code.
Then you can use Step Over and Step Into (look at the menu for the keyboard shortcuts)
I found a solution, but not the problem.
How I fixed it:
I just created a template for each form, created a new project, and imported everything into the new project. One thing that I found useful is in the new project is to add an existing item (CTRL + D), and group select (maybe, don't know if you can) and select all the non-code/form/designer/etc. files (like text files or images) and then import them.
I have found a possible solution after I had the same problem.
You probably have more than one project in your solution (The main project, plus an "InstallShield" project",perhaps)
Make sure you have the main project set up as "Startup Project".
In the Solution Explorer, right click on the Main Project and select "Set as Startup Project".
Everything will then run OK.
If you get the error like: "The debug mode is program but there is no program specified....." Go to Solution Explorer then Right Click on main project's name and Click on Set as StartUp project. You can debug your program.
I need to be able to edit vb.net code using visual studio without stopping the debugging executable.
How can I go about doing this? If it's impossible, how can I code and reload that code without stopping the executable? I know of scripting languages like Lua, but I fear the implementation of another language within the VB is unnecessary to save me the trouble of stopping the executable.
The issue is that starting and stopping this executable can take a very long time, and I need to be able to edit the code quickly and frequently.
I think you're talking about "Edit and Continue" which can be enabled in VS2010 > Tools > Debugging > Edit and Continue.
Note: the application must be in "break" mode to enable editing. When you talk about "Stopping the executable" do you mean stopping all debugging or stopping at a breakpoint?
Edit + Continue has been supported since VS2005. It won't work by default when you run on a 64-bit operating system, only 32-bit code is supported. Easy fix: Project + Properties, Compile tab, scroll down, Advanced Compile Options, change the Target CPU combobox to "x86". That's the default now for new projects created in VS2010.
Not every type of code change is supported by E+C, details are in this MSDN Library page.
Its easy, Edit and Continue is supported from VS1.1 up. The trick is placing a breakpoint in your code by clicking the left margin of a code window on a line of code you wish to halt the program. You will need to run the program in Debug mode (not release mode).
Tip you can also press Ctrl + Alt + PauseBreak to halt the program in the middle of a lengthy operation.
Once the programs Code Control halts you are free to edit and continue.