The following behaviour appears only on the mac versions of IntelliJ IDEA. First discovered it in version 2015, but in the currently newest 2017.1 it's still the same (both community/commercial).
set a breakpoint and start the application in debug mode (in my case a Spring Boot application started with application debug)
--> for the first time after server start the execution stops at the breakpoint (correct)
click "Run to cursor" and continue with the execution
execute the same to run again into the same breakpoint
--> the debugger does not stop anymore at the breakpoint (incorrect)
It also happens sometimes, that if the breakpoint is removed, the cursor still stops at the line, where the breakpoint was before.
After a server restart, everything goes fine again until the first execution.
Of course the code wasn`t changed in the meantime.
For these reasons, the debugger on mac is practically unusable.
Any ideas, if it's a bug (would be weird not having it fixed since years), or am I doing something wrong?
Related
Since I upgraded to XCode 12, the following situation keeps happening:
When I click "Stop" on a running debug build, the build is being slowly stopped (takes 3-5 seconds), then after it has completed, my app is still running, but detached from XCode.
A workaround that I've found is to add a breakpoint anywhere in the code, then after it's reached, the process seems to attach normally on each subsequent build until I quit XCode. But this is time consuming and does not always work.
I do get this output message:
Message from debugger: The LLDB RPC server has exited unexpectedly.
Please file a bug if you have reproducible steps.
I am running: XCode 12, Catalina, macOS Swift project.
Any ideas? Is there a new setting in XCode that I missed?
As soon as I upgraded to BigSur 11.0.1, I started noticing that some of the UI components in STS 4.8.1 started to disappear (or let's say they don't show up, since as soon as I click in the area, where they are supposed to be located, they start to appear) - this can be observed in the History tab for example. Another issue appears during the Debugging - as soon the execution reaches any breakpoint the screen doesn't seem to be refreshed automatically and the current code line, where the breakpoint is, gets mixed with the previous code lines. EDIT: if I scroll the page (up/down) the screen gets refreshed and I am able to see the correct line.
Initially I thought that this could be due to the DevStyle plugin (the dark mode), but I uninstalled it completely and I tried again and the issues are still present.
I think there are a few fixes being implemented at the moment inside of the Eclipse platform to fix issues with Big Sur. We plan to ship a new release of the Spring Tools 4 for Eclipse as soon as the new Eclipse release is being available.
Please also feel free to raise issues at https://bugs.eclipse.org/ for the things that you observe on Big Sur.
I confirm that the issues are solved with the latest STS 4.9.0 release.
I have an issue in certain code only when built for "production".
This problem doesn't occur when in debug mode (Hitting the "Play" button to run the app).
So in order to debug this problem, I compiled the app and loaded to simulator. The problem does indeed reproduce as expected.
In XCode I can successfully attach to the running process by doing: Debug->Attach to process by PID or name" from my source code.
I am able to run commands in the LLDB console so I know that the debugger is connected to the app, but none of my breakpoints are working.
How is it possible to make the breakpoints work as expected in order to debug this issue?
Say I am debugging and accidentally go past the function I wanted to step into. Currently, I rerun the app again through xcode (apple+R) and have to wait for the app to load again. Is there a faster way? I looked into the stop command (apple+.) but when I load the app again from the simulator my breakpoints don't trigger.
Restarting is probably your best bet, but it sounds like you may simply have too many breakpoints set if you're mindlessly hitting "Next" by the time you get to the one you want. Try turning off some of the preceding breakpoints (particularly those in loops).
If the breakpoint is in a loop, and you really only care about it under certain conditions (why else would you skip past it?), try setting it up as a conditional breakpoint that will only stop when you need it to. Check the answer to this question for more info on how to do so.
Ok so what i understand from the question is this : you have some breakpoints into a function...you run the app from xcode ..it didn't go into that function...then you went to simulator and run it from there and the breakpoints didn't trigger.
If that what you ment by the question ..your problem is that when you run the app from the icon in the simulator that doesn't run in debug mode it runs in release mode-ish (with some minor differences) .The debug mode only works when it's directly started from xcode (so of course your breakpoints didn't trigger).
As for the loading speed..you can't do anything about that it loads as fast as it possibly can. I personally only build and run on the actual device ..and from my experience it takes 2~4 s from the time i hit run till the app loads completely. That being said i noticed that if you have a splash screen (Default.png) it takes 1~2 s more to load so what i do is just remove the Default.png from the project , delete the app from device, restart the device, restart xcode and the screen wont be loaded every time . It may not seem like much ..per build but on the course of a few weeks of development it ads up to minutes. Also..don't forget to add the Default.png when you release it ...i forgot once and app got rejected :)
I am trying to debug this Mono desktop software in Monodevelop.
I imported the SLN file, ran Build all with success, but when I press the Debug button I get this popup that stays waiting forever saying Waiting for debugger:
The output says:
User assembly '/home/nico/src/SparkleShare/SparkleShare/bin/SparkleShare.exe' is missing. Debugger will now debug all code, not just user code.
My first line of code is a Console.WriteLine whose output does not appear anywhere.
Am I doing something wrong?
Monodevelop 3.0.3.2 on Ubuntu 2012.10.
Nothing special appears on the console with monodevelop -v -v -v.
When I press Start Without Debugging instead of Start Debugging, the app crashes immediately saying The application exited with code: 255, but I need Debug to find where the problem is.
When I press Debug Application... and select bin/SparkleShare.exe, Monodevelop does nothing. The UI does not react in any way, it is like I pressed nothing.
When I run the application from command line, it runs fine (no crash), but Monodevelop does not react in any way, so I can't use it to debug:
mono --debug bin/SparkleShare.exe
Debugging in Monodevelop works fine with a solution created from scratch.
Here is a hack to debug in Monodevelop that works here, but it is quite painful, and unsupported.
Note: It is not the same problem as this question, which is about MonoTouch waiting for a phone simulator... the suggestions over there are about the simulator or updating XCode... no simulator nor XCode here.
MonoDevelop 2.8.6.3 is kinda old.
I recommend you upgrading to 3.x or even the master branch, which has a lot of improvements and probably fixes your issue.