You'll see exactly the described behavour if you configure Eclipse to use javac for compilation. You see different behaviour in Eclipse only because it uses its own compiler which is free from this problem. The javac shouldn't have assigned the different line number to that instruction. So when stepping, debugger encounters jump instruction with the different line number and decides to stop at it (because the line number has changed). This is not the first report about well-known old javac problem: for some try/catch and if/else structures it generates several bytecode instructions, which are wrongly associated with line numbers. this will automatically create a new Java remote debug configuration and. You can configure IntelliJ to use the Eclipse java compiler, which may solve your issue. Jetbrains License Login If you have already installed IntelliJ IDEA We are. Once removing, you may need to Sync the project and do Maven > Reimport. ) to search for the module name which is stored in Intellij *.iml file in each module. If you do not know which modules have the debugged module jar as dependencies, you can use some tools (Eg. To solve this, simply remove the jar of the debugged module from all modules' dependencies in the Project Structure. This problem can occur even when the debugged module is called from other modules that do not depend on the debugged one. In Project Structure (Ctrl+Alt+Shift+S) > Modules, if you have added any jar of the debugged module to any another module's dependencies, Intellij might use the decompiled version of that jar instead of the latest source code, so the execution will pause at a breakpoint in the decompiled version instead. This problem could be similar to this issue. Modify the sed part if they're going somewhere else. This assumes your compiled class files are going into a build directory. zshrc and run deletebuilds within your project directory: alias deletebuilds='find. Testing support gives you an easy way to perform manual endpoint testing with the built-in HTTP client, as well as creating test. UPDATE: I've found this to be a randomly recurring issue so I created an alias to do the deletes if you're running a Bash-equivalent. Debugging, Testing, and more With context-aware debugging support, IntelliJ IDEA provides helpful visualizations of plugins and phases in the stack frame, as well as folder internals of Ktor in stack traces. I guess this is IntelliJ's version of that. I remember in Eclipse I always had to deal with the Eclipse Dance. Ultimately, I just ended up removing all the build and out directories in the project, tried running the test again and finally picked up the current source version. class file and it looked like the correct version. I have tried every combination of File -> Synchronize, Build -> Clean project, gradle clean build, etc. I've been fighting with a similar issue with a Gradle-based project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |