Thanks for the jdwpspy suggestion; I'll collect some more data when I
get a chance. Debugging-the-debugger is just my cup of tea, though
normally I have the sources at hand. (Grabbing the full Android
sources is on my to-do list).
However, your test case isn't one that I would expect to reproduce.
Instead of "throw new ArithmeticException()", which isn't really any
different from cases I know to work, try the OP's case:
int b = 0;
int a = 1/b; //ArithmeticException
That's when I observed the problem. My theory is that it is specific
to handling of low-level arithmetic, rather than the normal user-code
throw. Just a theory, but more plausible than the idea that the bug is
more pervasive.
(Of course, the "observer error" explanation is still on the table, as
always).
BTW, a documentation suggestion: Most of the stuff in the Dalvik
Debugger Support document you pointed me at is only going to be of
interest to geeks like me, but some of it is helpful for anyone trying
to debug -- the synchronized method handling, the merging of return
instructions, performance differences, etc. And one I noticed (and
expected) but don't see documented, though it touches on a special
case of it: variables can disappear as you step in the code, when
their values will never be used againn. From register optimization, I
expect.
I think a brief article with the highlights -- including points like
the debug protocol being debugger-agnostic -- would be a good addition
to the developer documentation. Perhaps extend the "Debugging Tasks"
article a bit.
On Feb 12, 3:11 pm, fadden <fad...@android.com> wrote:
> Two other thoughts:
>
> (1) I've seen Eclipse display the exception defined by the Android
> classes and the exception defined by some other VM (either its own or
> whatever JDK is configured). Make sure you've got the right source
> for the exception. Since ArithmeticException is working for you I'm
> guessing this isn't at issue, but figured I'd mention it.
>
> (2) If you're really curious you can use "jdwpspy" to do a man-in-the-
> middle dump of JDWP traffic. It sits between DDMS and the debugger.
> It's not a lot of fun to debug the debugger, but it's there if you
> find yourself drowning in free time and a desire to do marginally
> unpleasant things.
--
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
