February 01, 2011
Mark Wielaard: New GPG key.
Finally created a new GPG key using gnupg. The old one was a DSA/1024 bits one and 8 years old. The new one is a RSA/2048 bits one. I will use the new one in the future to sign any release tarballs I might create. pub 2048R/57816A6A 2011-01-29 Key f...
More »
February 01, 2011
Andrew Hughes: [SECURITY] IcedTea6 1.7.8, 1.8.5, 1.9.5 Released!.
We are pleased to announce a new set of security releases, IcedTea6 1.7.8, IcedTea6 1.8.5 and IcedTea6 1.9.5.
This update contains the following security updates:
The IcedTea project provides a harness to build the source code from OpenJDK6 u...
More »
December/2024
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | | 8 | 9 | 10 | 11 | 12 | 13 | 14 | | 15 | 16 | 17 | 18 | 19 | 20 |
21 | | 22 | 23 | 24 | 25 | 26 | 27 | 28 | | 29 | 30 | 31 | | | | |
|
 |
I got my first Android crash report
The crash report feature collects unexpected exceptions from an Android apps and delivers it to the Development Console where the app author can analyze it. It is only available on Android 2.2, which is not yet widespread, so until today I've never seen a crash report. This morning I received one. It's a trivial error I made since the very first version of the application, with no effects on the application, but that triggers an exception starting from Froyo.It's nice to see this kind of diagnostics (it would be even nicer if one received also the last ten lines of logging, in any case I suppose that this can be done with some explicit coding).
Date: August, 12 2010
Url: http://www.java.net/blog/fabriziogiudici/archive/2010/08/12/i-got-my-first-android-crash-report
Others News
|
