Thursday, May 19, 2011

[android-developers] Re: ADT debugger always stops at ALL exceptions

Eric,

I can reproduce the problem with uncaught exception on both: emulator
and device (Android 1.6).
However, debugger doesn't stop on caught exception.
As you, preferences don't distinguish.
Maybe you got some hidden uncaught exception.
Try to add android source ?

Regards,
Peco

On May 19, 4:00 pm, Eric Rizzo <eric.ri...@gmail.com> wrote:
> Rick,
> Like I said, I'm no newbie to Eclipse. I don't WANT to stop at all
> breakpoints, but with or without an Exception breakpoint it's stopping
> all the time. Doesn't matter if I set up an exception breakpoint with
> or without checking "caught exceptions."
> Debugging an Android device is behaving differently than standard Java
> debugging in this fundamental way. I'm just trying to determine if its
> a bug or something that can be configured, or something I'm doing
> incorrectly.
>
> Eric
>
> On May 18, 7:39 pm, Rick Alther <rick.alt...@gmail.com> wrote:
>
>
>
>
>
>
>
> > This is basic Java debugging in Eclipse.  In Java or Debug perspective:
>
> >    - Run->Add Java Exception Breakpoint.
> >    - Uncheck "Suspend on caught exceptions"
> >    - Click OK
>
> > You can also filter which exceptions you wish to break on here as well if
> > you choose.

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate