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. Android 2.0 SDK & Bluetooth

Very, very new to Android app-programming here.  From what I've seen
so far, it reminds me a great deal of Flex programming -- so I thought
maybe I'd give it a go, since I know Flex fairly well.

With that in mind, I have a specific question about the new 2.0 SDK:
Is it possible to have access to the Bluetooth API's necessary to
write an app that would allow voice-dialing via a BT headset?  I'm not
yet familiar enough with the SDK to answer this question for
myself...  I figured maybe there'd be someone out there who's familiar
enough with the new SDK to answer this question quickly.

Thanks,

-- 

2. Cannot debug using emulator with DROID skin

Just setup Eclipse, ADT, SDK, and DROID skin.  Set path to include SDK
tools directory.

Wrote the Hello World (Hello Android) app.  I can run the app,
emulator starts, but app does not start.  If I go into applications, I
can manually run the application and it works properly.  The app
should be loading as the documentation suggests.

I then added the null pointer reference and a breakpoint to test
debugging.

When I debug, same thing happens.  Emulator loads, app does not load.
If i manually run the app, it does not break at the breakpoint.

When I debug, I get an error in Eclipse:
Emulator]emulator: ERROR: unexpected qemud char. channel close
HelloAndroid]emulator-5554 disconnected!  Cancelling
'com.test.helloandroid.HelloAndroid acitivity launch'!


-- 

3. Fetching Android system software version

4. Error when trying HelloTimePicker Android Tutoral

5. android WiFi

6. GPS - GMaps Sample?

7. How to Retrieve Phone Owner's Email