How to activate logging in Nemiver
Nemiver logs are filtered using what are called logging domains.
Each logged message can be associated to a logging domain. Later on, when a user activates a logging domain, it enables the log messages associated to that domain to be dumped on stdout, for instance.
Logging domains can have arbitrary names. By default when a log message is issued by a source code file named "foo.cc", it is associated to a logging domain named "foo.cc". But again, logging domains can be named following arbitrary schemes.
How to activate the logs of a given domain
Just set the environment variable NMV_LOG_DOMAINS before you launch nemiver. Like this:
NMV_LOG_DOMAINS=main.cc nemiver > log.txt
This dumps the log messages emitted by the source code file main.cc. The resulting log messages are stored in the log.txt file.
You can activate several log domains as well, like this:
NMV_LOG_DOMAINS="main.cc nmv-workbench.cc" nemiver > log.txt
This dumps the log messages emitted by source code files "main.cc" and "nmv-workbench.cc".
Please find below the a quick list of how to activate logging for a typical set of use cases.
quick examples of logging activation
to log messages related to the communication with gdb:
NMV_LOG_DOMAINS="nmv-gdb-engine.cc gdbmi-output-domain" nemiver > log.txt
to log messages related to the main debugging GUI:
NMV_LOG_DOMAINS="nmv-dbg-perpective.cc" nemiver > log.txt
to log messages from all logging domains:
NMV_LOG_DOMAINS=all nemiver > log.txt
. But please, do that only if really needed because it really dumps a lot of messages.