Menu
I use last stable SBT with Scala 2.10 and last Scala plugin in IntelliJ IDEA 12.x. And have very simple test Scala project.
I have specs2 test where I want to start my debug from. Having several breakpoints, I'm expecting going over lines, (from one break point to another - in my test and in My code), but instead: the debbuger going somewhere inside library classes, stops there, showing me some strange sources.
That's reproducible all the time, and I have to click 2, 3, sometimes 5 times on the next-arrow-button (on debug panel) to reach next break point (in the test or in the code).
I run my test with SBT 'test-compile' action, like IntelliJ pop-up suggests.
Aldo I found this debug settings for Scala ("Do not step into specific Scala classes"). But I have this check-box selected.
I've post an issue in IntelliJ IDEA site.
754
To solve this, simply remove the jar of the debugged module from all modules' dependencies in the Project Structure. If you do not know which modules have the debugged module jar as dependencies, you can use some tools (Eg. Sublime Text, bash, ...) to search for the module name which is stored in Intellij *.
From the main menu, select Run | Force Step Over or press Alt+Shift+F8 .
Jump to a breakpointPress Ctrl+Alt+F9 or choose ReSharper | Navigate | Breakpoints… from the main menu . Alternatively, you can press Ctrl+Shift+A , start typing the command name in the popup, and then choose it there. In the Breakpoints popup that opens, you will see all breakpoints defined in your solution.
If you press and hold the Ctrl / ⌘ button while dragging the arrow, the IDE will highlight all the lines in green. When you drop the arrow, you won't jump to the line of code. Instead, the IDE will act as if you have used the Run to Cursor (⌥F9) action.
IntelliJ 15 now has support for adding breakpoints inside lambdas. See this blog post for details.
54
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
