On Thu, 14 Sep 2017 13:22:43 +0200
Tomasz Bursztyka <tomasz.bursztyka@...> wrote:

you discover CONFIG_NET_LOG_GLOBAL

[]

I have been using it when porting new devices, it's an easy option to
just see how
the whole behaves at boot/init time.

But indeed, it's not a good option when you need to debug an app.

It's off by default anyway. We can improve the doc there telling this
should not
be used unless the person knows what to do with it
i.e.: getting all errors/warning, but not on debug level!

Right, I had the same idea, mentioned in the other mails.

[]

As the name implies, the CONFIG_NET_LOG_GLOBAL is only for
networking. It might also miss some new net debug options.

Most probably yes

I posted https://github.com/zephyrproject-rtos/zephyr/pull/1507 showing
how this can be tackled in a scalable way (without introducing unneeded
Kconfig interdependencies, etc.).

Besides all that, debugging net stack is complex mostly because it's
a complex stack.

Yes, and we can make it simpler.

We could probably add a documentation about how to relevantly use the
logging options,
that's I guess the best to do right now.

Extending on what was said in the previous mails, people first want to
see stuff working (or telling them what's wrong), and then maybe
they'll dig into documentation. Seeing hangs and crashes in this age
will likely prompt "let's move on to something else" approach rather
than give encouragement to read long docs.

Tomasz

--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog