61a3e8c23a7c62c389433113802a0d74f4ab53cf |
|
27-Sep-2017 |
Andreas Gampe <agampe@google.com> |
Frameworks: Move Log holder to be preloaded To avoid issues with late initialization, let the holder be initialized in the zygote. Bug: 65927416 Test: m Change-Id: I6f454df46d4c64d295e1f2510793d5087b74fb74
/frameworks/base/core/java/android/util/Log.java
|
afeb63d823d4d9bfa48b31f284b2e668de30e5b5 |
|
29-Jun-2017 |
Scott Main <smain@google.com> |
Merge "add links to Log class summary for methods and logcat doc" into oc-dev am: ea6fea4d5d Change-Id: I205254f618a3a405aab6f783f5d7de99c9a3a907
|
450a5bb81cf62cc4e24b956d64e1d43f6875ba76 |
|
29-Jun-2017 |
Scott Main <smain@google.com> |
add links to Log class summary for methods and logcat doc bug: 29123084 Change-Id: Ida1351ca3647faa133905c5ff85df716bffd3203
/frameworks/base/core/java/android/util/Log.java
|
5e253647ad609fb67acd0bd25aca98018c340edd |
|
27-Apr-2017 |
Mukesh Agrawal <quiche@google.com> |
Merge "Log: increase visibility of Log.TerribleFailure"
|
c2a56b279eb418cf48bdb96da21c75ea7b25a741 |
|
17-Apr-2017 |
mukesh agrawal <quiche@google.com> |
Log: increase visibility of Log.TerribleFailure The Log.setWtfHandler() provides a way to override the default TerribleFailureHandler, so that we can test that a piece of code reports as terrible failure as expected. Unfortunately, we can't actual use setWtfHandler() at the moment. The problem is as follows: 1. The Log.setWtfHandler() method requires a Log.TerribleFailureHandler instance. 2. The Log.TerribleFailureHandler interface requires subclasses to implement a onTerribleFailure() method. The method requires a Log.TerribleFailure argument. 3. Log.TerribleFailure is a private inner class. Given the above, classes outside of Log can't create an appropriate argument to pass to Log.setWtfHandler(). To resolve this, we update the visibility of Log.TerribleFailure to be the same as that of Log.setWtfHandler(), and Log.TerribleFailureHandler. Test: m -j32 Bug: 37425059 Change-Id: Ie646b931869582398d61495e367e0d36e767a3e3
/frameworks/base/core/java/android/util/Log.java
|
c9668a18055e56848d1aea51778eef06a4da39ad |
|
07-Apr-2017 |
Mark Salyzyn <salyzyn@google.com> |
jni: isLoggable: adapt to removal of property name size limit (cherry picked from commit 8143fa57adfbb4a5cc253e4ef68663525a8f81eb) There is no longer a name size limit to the properties, remove illegalArgumentException if tag length is too large. Test: build Bug: 36696208 Change-Id: I4b4329c8c951082ed0d777cdd70ee3e773bed16c
/frameworks/base/core/java/android/util/Log.java
|
8143fa57adfbb4a5cc253e4ef68663525a8f81eb |
|
07-Apr-2017 |
Mark Salyzyn <salyzyn@google.com> |
jni: isLoggable: adapt to removal of property name size limit There is no longer a name size limit to the properties, remove illegalArgumentException if tag length is too large. Test: build Bug: 36696208 Change-Id: I4b4329c8c951082ed0d777cdd70ee3e773bed16c
/frameworks/base/core/java/android/util/Log.java
|
f8880561e67e1da246970b49b14285efd4164ab1 |
|
26-Feb-2016 |
Jeff Sharkey <jsharkey@android.com> |
When system server goes down, crash apps more. Similar to first patch, but now using new "rethrowFromSystemServer()" method which internally translates DeadObjectException into DeadSystemException. New logic over in Log.printlns() now suppresses the DeadSystemException stack traces, since they're misleading and just added pressure to the precious log buffer space. Add some extra RuntimeInit checks to suppress logging-about-logging when the system server is dead. Bug: 27364859 Change-Id: I05316b3e8e42416b30a56a76c09cd3113a018123
/frameworks/base/core/java/android/util/Log.java
|
d888beb9bfca2da6bba303cd7db809ccefa7b996 |
|
18-Feb-2016 |
Andreas Gampe <agampe@google.com> |
Frameworks/base: Use Log.printlns in RuntimeInit Make printlns in Log public-@hide so it can be used. Print uncaught exceptions that will terminate the process in RuntimeInit using printlns, so that long exception traces are not being truncated. Bug: 27245306 Change-Id: Ib24635f0ebdd80bd125e367302cab6a78e6a210a
/frameworks/base/core/java/android/util/Log.java
|
8413db8c36f4ba5979cdc2b1c3e1429e6ba34d6a |
|
14-Dec-2015 |
Andreas Gampe <agampe@google.com> |
Frameworks/base: Change android.util.Log multiline logging To avoid long stacktraces being truncated, add code to split up large chunks along line breaks. Introduce LineBreakBufferedWriter to chunk up log output. Add a core test for it. Change-Id: I34160fbce853c21329f7fa109a9c42506b2066af
/frameworks/base/core/java/android/util/Log.java
|
2d073ba83c570466a7f77d1cd9193ab4a60eaee4 |
|
09-Jun-2015 |
Christopher Ferris <cferris@google.com> |
Change wtf errors from ASSERT to ERROR. Calling println_native with the value of ASSERT will set the abort message. Unfortunately, there are numerous cases where one thread aborts, but before that thread can communicate with debuggerd, another thread calls wtf, which overwrites the abort message from the original failing thread. Fix this by changing this to an error level log message. Bug: 21490722 Change-Id: I9500e2e63eea96722602fdd46c86939c001a7c65
/frameworks/base/core/java/android/util/Log.java
|
1e01d16982e6b22ec4c0e2d6dc1e261eb6f92c8e |
|
05-Dec-2014 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #17323751: Additional items in aggregated battery stats - Now aggregate number of times each process has crashed and ANRed. - Now aggregate total number of connectivity changes. - Now record connectivity changes in the history. Crash and ANR counts are new entries at the end of "pr" in checkin. Connectivity change counts is a new entry at the end of "m" in checkin. Connectivity changes in the history checkin are Ecn and include the type of connection and its state. Change-Id: I0c01186446034cf6c3fb97d45f5e3b5c69a0438a
/frameworks/base/core/java/android/util/Log.java
|
5232271a41323594ae406be7476b6ca2f08af3d8 |
|
27-Aug-2014 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #17146552: system anr Add a safe path for Slog.wtf that doesn't acquire an activity manager lock or block in any way. Change-Id: I8fef8251a0cb85081442cae55d85063944248d15
/frameworks/base/core/java/android/util/Log.java
|
69eb6f57e34fb78050adcedcda8479cf2ad0c418 |
|
09-Apr-2014 |
Mark Salyzyn <salyzyn@google.com> |
Native Runtime: Add LOG_ID_CRASH Change-Id: I4e3a82636901c5169cc6b714a4fec815cd757c58
/frameworks/base/core/java/android/util/Log.java
|
878deb3c7b33a0c508137143c776e07bab0296cf |
|
15-Oct-2013 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #11223335: APR: Lots of failures in procstats due to... ...bad cleanup of crashing processes We now have a special path for crashing processes, to silently clean up their state. Also some tweaks to Log/Slog.wtf to get better stack crawl summaries in APR. Change-Id: Ieced26989907a6e7615b6fa033813fced78d7474
/frameworks/base/core/java/android/util/Log.java
|
164371fb759bad6854570af0fca60d9a01e17235 |
|
02-Oct-2013 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #11005453: [SUW] G+ profile creation for new user broken The main problem here was a mistake when turning a single process structure to a multi-package-process structure with a common process. When we cloned the original process state, if there were any services already created for the process for that package, they would be left with their process pointer still referencing the original now common process instead of the package-specific process, allowing the active counts to get bad. Now we switch any of those processes over to the new package-specific process. There was also another smaller issue with how ServiceRecord is associated with a ServiceState -- we could be waiting for an old ServiceRecord to be destroyed while at the same time creating a new ServiceRecord for that same service class. These would share the same ServiceState, so when the old record finally finished destroying itself it would trample over whatever the new service is doing. This is fixed by changing the model to instead of using an "active" reference count, we have an object identifying the current owner of the ServiceState. Then when the old ServiceRecord is cleaning up, we know if it is still the owner at that point. Also some other small things along the way -- new Log.wtfStack() method that is convenient, new suite of Slog.wtf methods, fixed some services to use Slog.wtf when catching exceptions being returned to the caller so that we actually know about them. Change-Id: I75674ce38050b6423fd3c6f43d1be172b470741f
/frameworks/base/core/java/android/util/Log.java
|
8c84109b9fbbf473b225707a38261ff5f99d95fb |
|
24-Jun-2013 |
Dianne Hackborn <hackbod@google.com> |
Use FastPrintWriter... everywhere. One problem this turned up is, because FastPrintWriter does its own buffering, a lot of code that used to use PrintWriter would fail -- if it pointed to a StringWriter, there was no buffering, so it could just immediately get the result. Now you need to first flush the FastPrintWriter. Also added some new constructors to specify the size of buffer that FastPrintWriter should use. Change-Id: If48cd28d7be0b6b3278bbb69a8357e6ce88cf54a
/frameworks/base/core/java/android/util/Log.java
|
dba50c7ed24e05ff349a94b8c4a6d9bb9050973b |
|
19-May-2011 |
Joe Onorato <joeo@google.com> |
Reduce log spew. Change-Id: I69c9d7227d6cb91eac3b9f18d9edaa121c86ad0f
/frameworks/base/core/java/android/util/Log.java
|
26d8fa9dbf1dfd859d215525b17650266e9f9bb0 |
|
15-Dec-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Put Log.wtf's terrible failure in logcat -b main. As discovered by jpa@, previously it was only in logcat -b events, not -b main, which people don't typically watch. Bug: 2964398 Change-Id: Id672dd936f1678dd347158428b0ca03e4ad1e2d4
/frameworks/base/core/java/android/util/Log.java
|
44dc76a8a702d6a919fcea1c2d19ba3792687c85 |
|
03-Jun-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Log.wtf when databases go to be downgraded. BUG=2734435 Change-Id: I686d6d9415f3081544c3fbe379287c31e0ecec20
/frameworks/base/core/java/android/util/Log.java
|
8a9b22056b13477f59df934928c00c58b5871c95 |
|
27-Feb-2010 |
Joe Onorato <joeo@android.com> |
Switch the services library to using the new Slog
/frameworks/base/core/java/android/util/Log.java
|
00bb93823d082c31d757bd7b75a8615afbd2c1a5 |
|
27-Feb-2010 |
Joe Onorato <joeo@android.com> |
Add new Slog class.
/frameworks/base/core/java/android/util/Log.java
|
6e70912bd53aaa5264259e160eb2b4d2eb0f302c |
|
07-Jan-2010 |
Dan Egnor <egnor@google.com> |
Bumper un-@hide (un-@pending actually) of previously reviewed APIs: - new Log methods for reportable conditions - EventLog publication, EventLogTags deprecation - a new stackTrace field in ProcessErrorStateInfo
/frameworks/base/core/java/android/util/Log.java
|
60d8762413e8daba5f73559786312a9ec5e3b827 |
|
17-Dec-2009 |
Dan Egnor <egnor@google.com> |
DropBox logging of app & system server crashes. The crashes are also reported to the event log (and of course the main logcat, like they always have been). Ordinary Log.e(t,m,e) isn't dropboxed but there's a new Log.wtf() which always is. (Still @pending in this change.) Add a hook to IPowerManager to crash the system server on demand (only for apps with REBOOT permission, since it's basically a restart). This is not exposed in PowerManager, must be invoked directly -- mostly this is there so "Bad Behavior" in dev tools can do it.
/frameworks/base/core/java/android/util/Log.java
|
b7f0367cec1c744aa66ef397b0244e25d507491c |
|
10-Dec-2009 |
Dan Egnor <egnor@google.com> |
Eliminate CrashData and friends. (CrashData was a custom-marshalled crash-info class used for a server crash reporting system I am deprecating). Use ApplicationErrorReport.CrashInfo instead to report crash details (mostly the stack trace) from RuntimeInfo to ActivityManagerService, since we're likely to need the crash information in that form anyway. Remove the (long-disabled) flags and support for the "Debug" button in the crash dialog. Further gut the ICheckinService interface by removing the crash-reporting APIs (and everything that calls them), plus the synchronous checkin() method (which has been stubbed out for a while now). A new dropbox-based crash reporting system is in the works, but not part of this change.
/frameworks/base/core/java/android/util/Log.java
|
9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/util/Log.java
|
d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/util/Log.java
|
9266c558bf1d21ff647525ff99f7dadbca417309 |
|
16-Jan-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@126645
/frameworks/base/core/java/android/util/Log.java
|
54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/util/Log.java
|