Frank, could this be the little snag I just encountered in replying to RustingInSeattle? Where it doesn't catch RuntimeExceptions thrown from the low level (or maybe any level), unless there's an exact match of class?
Can you try your scenario again, this time once you identify the exception class being thrown, set a breakpoint on that specific class, and repeat? I'm not sure exactly where the bug here would lie -- I don't think the ADT plugin supplies anything, so I think it would be on the Android/ SDK side. It's annoying, sure enough. Probably a bit less so if we know it's there, but it would be a real pain for difficult-to-reproduce bugs. Still, getting at the original stack trace, once it's finally printed somewhere, should get you back to your code. If something silently swallows that exception (retry code, perhaps), of course you're out of luck. On Feb 9, 6:38 pm, Frank Weiss <fewe...@gmail.com> wrote: > @Bob I don't think you really nailed the problem. I ran into what I think is > a similar issue. The stack trace showed the location of the throw deep in > the Android API, without a hint of a stack frame from my code. I suppose the > problem is because some of the Android code runs in different threads, so > that the exception was probably due to some data structure from my code that > the API later trips over in another thread. > > I tried downloading the Android source code and adding it the the Android > project source code path. This solved the "no source found" error in the > Eclipse debugger, but unfortunately, the source code line where the > exception supposably was thrown didn't show any reasonably rational Android > code. I suppose the reason might have been that I pulled down the wrong > version of Android source. > > In the end, my problems were due to not using the API correctly. In one case > it was trying to manipulate the UI from the AsyncTask.doInBackground method. > In another case it was because it was calling populate several times on a > Overlay object instead of just once after all the items had been added. > > I'd still like to see an answer to the OP because it might be quite > educating to step through the Android source code. I usually figure out what > went wrong by looking at the the code that actually threw the exception and > seeing the data structure that caused it to barf. -- 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
