> I was frankly operating under the assumption that tracking down the precise
> source would be futile and thinking it more pragmatic to look at the
> application code instead
You're right, that's a good assumption; it's usually the case that
some API was called with invalid arguments or in an illegal state and
investigating the last stack frame from your own application is the
first place to look. This isn't specific to Android development
obviously - almost anytime you're using a framework or library it's
almost always going to be something in your own code. On the other
hand, bugs exist and sometimes peeking at the library source code can
help you realize the problem more quickly, especially if it's an
illegal state issue rather than just an illegal argument issue.
--Tor
--
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
No comments:
Post a Comment