Log Filters | Citra | Nintendo 3DS Emulator
Read First!

The below wiki article is based on user submitted content.
Please verify all hyperlinks and terminal commands below!

See a mistake? Want to contribute? Edit this article on Github

Log Filters

Citra supports configurable filtering of log message per-class. This is especially useful if you’re debugging a subsystem and want very detailed messages from it or if you want to silence some annoyingly spammy errors (e.g. unimplemented GPU features.)

Messages are filtered in each class according to their severity, the filter will block all messages in the class that are below the configured severity. The severity levels are: - Trace: Extremely detailed and repetitive (many times per frame) debugging information that is likely to pollute logs. - Debug: Less detailed debugging information. - Info: Status information from important points during execution. - Warning: Minor or potential problems found during execution of a task. - Error: Major problems found during execution of a task that prevent it from being completed. - Critical: Major problems during execution that threathen the stability of the entire application. (This severity cannot be filtered out.)

Note that Trace is permanently filtered out in non-Debug builds for performance reasons.

Class names can be discovered from the log messages themselves. For example, this message is in the class Service:

[  10.285042] Service  core/hle/service/service.h:Service::Interface::SyncRequest:84: unknown/unimplemented function '0x01020000': port=APT:U

Otherwise, a complete list can be found in the source in log.h

Log Filters

To configure the log filter, edit the configuration file (either qt-config.ini or sdl2-config.ini) and change the log_filter setting. The filter string consists of a space-separated list of filter rules, each of the format :. is a log class name, with subclasses separated using periods. `*` wildcards are allowed and can be used to apply a rule to all classes . a severity level name which will be set as the minimum logging level of the matched classes. Rules are applied left to right, with later rules overriding previous ones in the sequence.

A few examples of filter rules: - *:Info – Resets the level of all classes to Info. - Service:Info – Sets the level of Service to Info (without affecting its subclasses). - Service.FS:Trace – Sets the level of the Service.FS class to Trace.