On May 22, 6:46 pm, Kevin wrote:
> Anyway, it crashes while restoring the state, but when it's killed the
> debugger detaches, so when it's restarted after the camera is done, I
> don't have a debugger to see what's causing the crash. I know what
> function is causing the crash but I can't see th
I looked at making a new remote application, but how do I know what
port to use and what do I put in for the host? I'm debugging it on my
phone since the emulator's camera doesn't work for me.
I'll try using Log.v too maybe I can figure it out with that.
On May 23, 11:21 am, Kacee wrote:
> You
You said your debugger detaches as soon as your activity gets killed.
Check if activity for camera and activity for your usual app runs in
separate process. You can check that in DDMS view in eclipse.
If thats the case, then you would need to do Debug Configurations ->
New remote Application -> Se
Log.v() is your friend. I tend to use it more than the debugger since
half the time I change any xml, my app crashes due to the Eclipse plug-
in problem. Since it's so useful, I went back to the primitive way of
debugging unless I really can't figure out what's going on.
On May 23, 9:46 am, Kevi
4 matches
Mail list logo
