There is a new "+debug" flag in this (3.4.0) ebuild which is enabled by default. Was it done in purpose? I compiled it without debugging and don't see why it must be enabled. Could you clarify? Thank you.
ok, I found an article https://www.infradead.org/~tgr/libnl/doc/core.html#_debugging which explains that even when debugging has been enabled during compilation, it is actually disabled by default and can be enabled using an environment variable. They should have called it a "debugger" or similar to avoid this confusion with common "debug" feature. Ok, closing the bug.
(In reply to Anton Bolshakov from comment #1) > ok, I found an article > https://www.infradead.org/~tgr/libnl/doc/core.html#_debugging > > which explains that even when debugging has been enabled during compilation, > it is actually disabled by default and can be enabled using an environment > variable. Right. > They should have called it a "debugger" or similar to avoid this confusion > with common "debug" feature. USE=debug has no common meaning, but in this case the global description is entirely correct: debug - Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces So no "debugger" is involved at all. You just get extra output. > Ok, closing the bug. Thanks. Also: --disable-debug Do not include debugging statements It's the upstream default.
(In reply to Jeroen Roovers from comment #2) > debug - Enable extra debug codepaths, like asserts and extra output. If you > want to get meaningful backtraces see > https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces In the global description, it should enable debugging symbols. That can make a code bigger and slower potentially. It might also pollute a system with unnecessary logs. That doesn't seem the case with this flag, that's why I got confused initially.
