Which version of the ADT and SDK you use? Which version of the Android
is on your device ?

Regards,
Peco

On May 18, 5:21 pm, Eric Rizzo <[email protected]> wrote:
> I'm a very experienced Eclipse user, but some behavior in the debugger
> with ADT is confusing and causing a lot of pain.
> Every time I'm debugging an app on a device, the debugger stops at ALL
> exceptions, even if they're eventually caught. I don't have any
> exception break points set up, which would be the expected cause if
> this were regular Java debugging.
> For example, I use a library that, for good or bad, generates some
> ClassNotFoundExceptions during its initialization. These are harmless
> and actually caught by the library, not even logged to LogCat. But the
> ADT debugger insists on stopping every time one of them is thrown. It
> makes debugging this app a real pain, because I have to Resume a bunch
> of times every time the app is launched.
>
> Is this intentional behavior of the ADT debugger? Is there a way to
> turn it off?

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

Reply via email to