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. send message(ex:location or other message) between 2 emulator

thank for your help.
And I have a new problem that  I want to send a message(ex: location)
from one emulator to the other.
Can I use socket or any android api ?

thanks-

--~--~---------~--~----~------------~-------~--~----~

2. Menus in SDK 0.9

Hello,
I read that menus are one of the improved areas in the new SDK.
I'm trying to do some example I found, but doesn't seem to work, as
the code is for the m5 SDK.

So, I read Android Docs online, and I tried this:

1) Override onCreateOptionsMenu()

    @Override
    public boolean onCreateOptionsMenu(Menu menu) {
                super.onCreateOptionsMenu(menu);
                menu.add(0, Menu.FIRST, Menu.FIRST, R.string.options_label);
                MenuInflater mi = new MenuInflater(getApplication());
                mi.inflate(R.layout.options, menu);
                return true;
    }

2) Create OPTIONS.XML layout (R.layout.options) with a linearlayout
containing 2 checkboxes in it.

I run this code and it warns me that the app closed unexpectedly.

Question: Do I have to create some openOptionsDialog() to associate to
the menu? If so, HOW?
In the m5 example, there was a Menu.Add() overload that included a
parameter to pass a Runnable() to the menu, but in 0.9 can't find it.

Thanks in advance,
Tony

--~--~---------~--~----~------------~-------~--~----~

3. Download Manager, filesupport ??

4. android dont avoid

5. Googlephone [HTCdream]: HW testing and what about Italy?

6. Errors when trying to build an example from a guide...how can I resolve.

7. app>dialog>textentry getting the EditText values