Hi, I've reverted this commit because I'd like to avoid adding env vars as workaround for things that other env vars can do (e.g., EINA_LOG_LEVELS). I have, however, replaced the intended functionality with something which should require even less effort for you to activate.
On Wed, Jun 21, 2017 at 9:35 PM Carsten Haitzler <[email protected]> wrote: > raster pushed a commit to branch master. > > > http://git.enlightenment.org/core/enlightenment.git/commit/?id=62feb358e6a9d4307bdeb72234a87bf0e3d8ccc1 > > commit 62feb358e6a9d4307bdeb72234a87bf0e3d8ccc1 > Author: Carsten Haitzler (Rasterman) <[email protected]> > Date: Thu Jun 22 10:34:16 2017 +0900 > > e - allow env var to turn off aborting at any CRI issue > > some of these CRI logs are not wirth an abort... but mike seems to > think so... so i'm going to turn it off for me... > --- > src/bin/e_log.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/src/bin/e_log.c b/src/bin/e_log.c > index dcbf96e1e..7446d0501 100644 > --- a/src/bin/e_log.c > +++ b/src/bin/e_log.c > @@ -40,7 +40,8 @@ e_log_init(void) > eina_log_print_cb_set(_e_log_cb, NULL); > } > #ifndef E_RELEASE_BUILD > - eina_log_abort_on_critical_set(1); > + if (!getenv("E_DONT_ABORT")) > + eina_log_abort_on_critical_set(1); > #endif > return e_log_dom != -1; > } > > -- > > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
