I am unable to attach debugger to my process. I am using Ubuntu 20. Before the new AS 4.1 everything was working. AS finds the process just fine, but when I click "OK" the breakpoint doesn't turn green and I don't see the debugger window/tab.
I don't have much information I can give about this issue, so if you need some log or I don't know what, please let know.
ok, turns out it was a really silly mistake on my part. There is a new drop down "Use Android Debugger Settings from:" which was set up wrong for me and therefore the debugger never attached... Hope that helps to someone
Related
I am trying to debug some OpenGL code, so I wanted to make use of the GPU debugger from Android Studio. For this I need to get a GPU trace, according to the steps detailed at https://developer.android.com/studio/debug/am-gpu-debugger-trace.html. But, after the dialog for trace name, Android Studio shows directly the message: Failed to attach to process.
Android Studio has version 2.3, and was recently updated.
On the device (Samsung S3) I see the alert: !Waiting for debugger.. process zzz is waiting for debugger to attach.
I tried to enable all GPU related options from developer options in device settings, also to disable all, with the same result. Is this feature working? My setup is not very uncommon.
I reached to a point where I get the message: The GPU debugger does not currently support tracing on this device. So the answer would be that it does not work on S3. I'll leave the question here, maybe it will save someone a few hours of investigation.
When trying to enable Run/Debug Configurations>Profiling>Capture GPU Commands, I was required to install "GPU Tools". Then, after accepting to install, it complained that they were already installed in the folder, and I should remove them prior to new installation. So I moved them away. Then it would give the error from the question.
After some attempts, I decided to put the contents of the folder back, deselect/select again Capture GPU. It said once again that I needed to install GPU tools, but this time I did nothing. The checkbox got checked anyway, and when trying to start the trace, went on to do some stuff without complaining about the attaching to the process. Finally it did not work anyway, but at least I know the reason.
Apologies if this has already been asked or not doable, but when I code in IOS or Eclipse I can make code changes even if the app is running on my device while testing some aspect. I then just rebuild and it restarts the app on the device with the modified code.
Is there a way I can do the same with Visual Studio 2012? It is very annoying if I forget to stop the device from testing the app and try type in code only to be prevented from making changes. Not a show stopper I know, but if there is a setting some where it sure would be helpful.
So in a nutshell, I want to run some code on my device (lumia 520), note an issue, make the change in MainPage.xzml.cs or elsewhere and then just restart the build and it will stop the app running on the device and restart it with the modified code.
I will keep looking myself but as it always the case, sometimes its harder to find the right question to ask than get to the answer. Hope the question makes sense and appreciate any suggestions.
Seems as its a default way Visual Studio works as I get the same issue with Visual Studio 2013. Could not find anything in OPTIONS so will leave it at that.
I'm wondering if anyone else has seen this issue and has a fix for it? The problem is with VS 2012 Ultimate where when it has been minimised or the lock screen has covered it it appears as shown in the attached screenshot.
This is the only application on my system (Dell E6510 running Windows 8) that exhibits these symptoms so I'm inclined to lay the blame at the application's feet rather than the system.
Playing around with the following settings appears to have resolved the issue for me. Your kilometerage may vary
If I check then uncheck any of those options it works until I close it, then you have to repeat again next time.
So did more research and found this mentioned on MS Connect site...
"I had a quick look at the "Extensions" running in VS2012, and noticed one I remember magically appearing without me really asking for it. HDInsightTools for Azure."
I removed that and all works! :) So maybe you need to review Extensions installed?
I have a Lightswitch 2012 application. It's been working fine for weeks. I made some changes and F5 stopped working. When I click on Start (toolbar) it gives this error message and does nothing.
"The Debugger cannot continue running the process. Unable to start debugging"
Note: It does compile file, it just doesn't run.
If I rollback to an earlier version then it works fine - i.e. it is solution specific.
Here is a video of the current version of my solution with the problem:
http://screencast.com/t/TD4RzLASO
and here is the previous version of the solution from earlier today (and no, I don't know what I changed). As you can see, at least it does something with F5 or Start:
http://screencast.com/t/wX5fRDPz
Rebooting doesn't help... ;)
Maybe you should select start up project which can be started.
Solution Explorer -> On your startable project right mouse click -> Set as Start up Project.
I had this situation when i unloaded my main lightswitch project and other project which is dll has been selected automatically and when i reloaded my main project "The Debugger cannot continue running the process. Unable to start debugging" exception was shown, because debuger was trying to load DLL.
Sometimes you need to start up a project which is compiled as a dll, for instance when testing WCF services.
To do so:
Projects -> 'Set Startup Projects...' -> Select 'Multiple Startup Projects' and set action to 'Start' for each one.
It's a pity you didn't recorded the whole screen, so I can't confirm, but I had the same error a few times...
When this happens, my "output panel" isn't visible and even I try to go on Menu -> View -> Output the panel don't appear.
I need to restart my Visual Studio 2013.
Then my output panel is visible again and everything works fine.
I discovered the cause was an extension which I installed on my Visual Studio.
I encountered this problem after removing some projects from the solution. I wasn't able to pinpoint the exact cause, but closing the solution, deleting the solution file, then opening the project and re-adding supporting projects solved the issue for me. Kind of a sledge hammer, but only takes a minute to do if you don't have a lot of projects.
Also, there are some people that uses a "One Click" Certification in your settings that you'll want to make sure its set up right, re-install or unchecked in-which this case was my problem. I finally got it working myself, but check that too just in case. Again this would be for most Visual Studio Versions only. Im 2013 Ult.
I download the Android code and "make sdk" to build out my own SDK, but the emulator from this SDK does not work well -- it only shows the black window with the "ANDROID" string, but I can't see any desktop picture or any applications. what's wrong here? anyone could please provide me a hint? Thanks a lot.
I use the command:
$./emulator #jiawelin -debug all
and the last output message is:
emulator: android_hw_control_init: hw-control qemud handler initialized
It's working, just give it time. The Android emulator is ridiculously slow to start up, especially if your computer isn't the fastest. Wait for a few minutes and it will eventually load.
(I know this reply is very late, but I just had the same problem - hopefully this will be useful to anyone else who finds this question through a search engine)
The latest emulator in tools versions 18+ have a known problems that exhibits for some. Kill the emulator and restart it with the same AVD. Give it some time to boot this second time and you should be good to go.