问题
After upgrading Samsung Galaxy S5 SM-G900F to Lollipop (Android 5.0) I noticed strange behavior:
not all breakpoints are being caught within Android Studio.
Here is environment description and my observations
- Windows 8.1 x64
- Android Studio 1.0.2 with SDK Tools 24.0.2
- Sun jdk1.7.0_55
- under SDK emulator all breakpoints are caught
- under Genymotion all breakpoints are caught
- under Galaxy S3 with 4.4.4 all breakpoints are caught
- under Galaxy S5 SM-G900F with 5.0 not all exceptions are caught
I tried rebooting phone, rebooting dev machine, turning on/off debugging in dev options, using USB drivers from Samsung and Google, invalidating cache in Android Studio, doing full clear and rebuild and so on.
Breakpoints that work have ticks inside red icons. I don't know the rule, which classes do have working breakpoints and which don't.
The same thing happens with this device on three different devboxes.
Help!
回答1:
Last update of Samsung S5 this week solves the problem with Eclipse IDE. Android French version G900FXXU1BOC7
回答2:
I found this out: Breakpoints don't work on allocations in some versions of Android. An allocation (second image) isn't executable code but the Fabric init code is, so it can break at that point. It seems to be a sort of check if the code is executable or not.
来源：https://stackoverflow.com/questions/27940583/galaxy-s5-lollipop-not-all-breakpoints-stop-execution-under-android-studio-deb