NSS:Tracing: Difference between revisions
(Report the related bug number) |
(Add bug number for OCSP issue) |
||
| Line 16: | Line 16: | ||
It appears, you must enable logging for at least one module. It appears to be sufficient to request logging for any module, even if that module doesn't exit. If you're not interested in any other log output, you might even use NSPR_LOG_MODULES="any_random_string:5" | It appears, you must enable logging for at least one module. It appears to be sufficient to request logging for any module, even if that module doesn't exit. If you're not interested in any other log output, you might even use NSPR_LOG_MODULES="any_random_string:5" | ||
This is the subject of [https://bugzilla.mozilla.org/show_bug.cgi?id=429052 bug 429052]. | |||
[[Category:NSS]] | [[Category:NSS]] | ||
Revision as of 00:22, 15 April 2008
This page is meant to collect the various mechanism used to trace the runtime behavior of NSS. It might be necessary to use a debug build.
libPKIX
libPKIX uses the PR_LOG macro with log module name "pkix".
You may enable logging output using NSPR_LOG_MODULES="pkix:5"
In addition, you may have to use NSS_STRICT_SHUTDOWN="x" to ensure the pkix log module gets activated. This is the subject of bug 429039.
OCSP
OCSP tracing uses PR_LogPrint.
NSS_TRACE_OCSP="1" is supposed to enable OCSP tracing. However, it's not sufficient.
It appears, you must enable logging for at least one module. It appears to be sufficient to request logging for any module, even if that module doesn't exit. If you're not interested in any other log output, you might even use NSPR_LOG_MODULES="any_random_string:5"
This is the subject of bug 429052.