[android-developers] Re: Weird stack traces on Honeycomb

My code appears in the stack trace although these errors

- happen only on Honeycomb. Mostly 3.0.1, sometimes 3.1, never saw one
for 3.2
- happen in basic data structures
- they are rare

another one still on the A500 that makes no sense:

java.lang.NullPointerException
at java.lang.String.lastIndexOf(String.java:1194)
at java.util.concurrent.locks.ReentrantReadWriteLock
$ReadLock.unlock(ReentrantReadWriteLock.java:854)
<app specific backtrace here>
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1081)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:574)
at java.lang.Thread.run(Thread.java:1020)

So at this point I suspect that either the backtrace is bogus and
cannot be trusted (since I can't see the Honeycomb code, it is
impossible to verify),
or some versions of 3.0.1/3.1 are broken for some users maybe only in
some cases (otherwise nothing would work).

On Aug 21, 12:23 pm, Mark Murphy <mmur...@commonsware.com> wrote:
> When you say "they happen in the platform", do you mean that your code
> appears nowhere in the stack trace?
>
>
>

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en