jpeg pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=65b53f4a3737196a9caf100e06ccebfa0aed8e87
commit 65b53f4a3737196a9caf100e06ccebfa0aed8e87
Author: Jean-Philippe Andre <jp.an...@samsung.com>
Date: Tue May 12 19:00:57 2015 +0900
Eina log: Enable backtrace only for CRI and ERR by default
Using EINA_LOG_LEVEL=4 for standard debugging has now become
absolutely horrible (and slow!). Backtraces may make sense in
case of ERR and CRI messages, but are just pollution for other
levels.
WRN could be argued over but the old env variable is still there
so just use it if you want backtraces:
$ export EINA_LOG_BACKTRACE=2
---
src/lib/eina/eina_log.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/lib/eina/eina_log.c b/src/lib/eina/eina_log.c
index 5f458f0..a9eb9aa 100644
--- a/src/lib/eina/eina_log.c
+++ b/src/lib/eina/eina_log.c
@@ -121,7 +121,7 @@ static Eina_Bool _disable_timing = EINA_TRUE;
static int _abort_level_on_critical = EINA_LOG_LEVEL_CRITICAL;
#ifdef EINA_LOG_BACKTRACE
-static int _backtrace_level = 999;
+static int _backtrace_level = 1; // CRI & ERR by default
#endif
static Eina_Bool _threads_enabled = EINA_FALSE;
--
