Since day 1 running enlightenement, ~April 2017. Anytime I am running stuff in a terminal or worse doing development. I constantly get useless output that is not useful or beneficial in any way. It just creates more noise and stuff to filter through. I have yet to be able to use it to find any real information or issues. See the following output from entrance log.
Most of the output translates to
/usr/lib64/libeina.so.1 | ??/??: 0 @ _eina_semaphore_free() /usr/lib64/libeina.so.1 | ??/??: 0 @ eina_log_print_cb_stdout() /usr/lib64/libeina.so.1 | ??/??: 0 @ eina_log_print() /usr/sbin/entrance | / : 0 @ () /usr/lib64/libecore.so.1| ??/??: 0 @ ecore_event_add() /usr/lib64/libecore.so.1| ??/??: 0 @ ecore_main_fd_handler_add() /usr/lib64/libecore.so.1| ??/??: 0 @ ecore_main_loop_begin() /usr/sbin/entrance | / : 0 @ () /lib64/libc.so.6 | ??/??: 0 @ __libc_start_main() /usr/sbin/entrance | / : 0 @ ()
It basically has become so useless I almost never copy and paste the output. I am now looking into stopping it entirely via EINA_LOG and maybe EINA_LOG_LEVEL. I have to look into that, but something seems off and less than ideal. By default it should not be spitting stuff out. When I encounter real issues, crashes etc. It really munges the output, as the copy/paste bit is wrapped around the crash output.
This may be a result of setting
Either way if possible should be reviewed and improved. Most of the time the output is the exact same as above and not sure what that is saying. Nothing useful it seems. I see little to no difference when I build entrance with debugging symbols. I have tried to build EFL with debugging symbols but it causes major problems. Makes many EFL apps and E itself non-functional. I had lots of errors about locks, and many things stopped working and generated a lock related error. But that is another issue.