ADT debugger always stops at ALL exceptions

by Eric Rizzo » Wed, 18 May 2011 23:22:06 GMT


Sponsored Links
 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?

-- 



Re: ADT debugger always stops at ALL exceptions

by snpe » Thu, 19 May 2011 02:33:45 GMT


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

Regards,
Peco




-- 


Sponsored Links


Re: ADT debugger always stops at ALL exceptions

by Eric Rizzo » Thu, 19 May 2011 02:42:27 GMT


 Sorry, forgot to include the version info.
Eclipse Helios (3.6), ADT 10.0.1.
My SDK installation includes all releases from 3-11, my project
targets 7 (Android 2.1-update1). Device has 2.2.2.






-- 



Re: ADT debugger always stops at ALL exceptions

by Rick Alther » Thu, 19 May 2011 07:40:09 GMT


 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.

-- 



Re: ADT debugger always stops at ALL exceptions

by Eric Rizzo » Thu, 19 May 2011 22:00:54 GMT


 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





-- 



Re: ADT debugger always stops at ALL exceptions

by Rick Alther » Thu, 19 May 2011 23:03:54 GMT


 In my experience there is no difference debugging an Android application 
than any other Java application.  When I uncheck that preference, I no 
longer stop at any exception that is caught.  If it's still breaking on any 
caught exceptions after that preference has been unchecked, then I am at a 
loss, since that's not my experience.  Have you tried another machine to see 
if it's reproducible there?

- Rick

-- 



Re: ADT debugger always stops at ALL exceptions

by snpe » Fri, 20 May 2011 07:35:25 GMT


 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





-- 



Other Threads

1. Apple: iPhone 4 reception problem is a software issue, fix coming in 'a few weeks'

fyi..for iphone users..hanya info sja..

http://www.engadget.com/2010/07/02/apple-iphone-4-reception-problems-a-software-issue-fix-coming/

-- 
"Indonesian Android Community [id-android]" 

2. Replicating fastscroll like in contacts

I'm looking for a tutorial on implementing the fastscroll feature
found in the contacts view. I'm using a ListActivity with a custom
array adapter to display my list (I use subtext under the main text
info).

I've seen the List9.java class in the samples directory, but it's not
the easiest example for me to follow -- I'm not ashamed to admit the
concept of the subclassed array adapter baffles me, even though it
works quite nicely. All my attempts to use this have ended with a FC
and an unceremonious boot to the desktop.

Is there one good example out there that explains things? Failing
that, maybe different examples? I'm listing songs on the sd card...you
know, the usual.

Ken

-- 

3. Accuracy of location.getAccuracy() GSM and GPS - exact Meaning?

4. Accuracy of location.getAccuracy() GSM and GPS - exact Meaning?

5. Desire Froyo UPDATE OTA

6. Please read: Eclipse 3.6 compatibility issue

7. java.lang.NullPointerException when trying to edit strings.xml