N-archive/citra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Revert 20c29df^...20c29df on Log Filters

archshift 2015-04-05 02:23:16 -07:00
parent 20c29df311
commit f51dd643e9
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
Log-Filters.md

@ -1,4 +1,4 @@
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 spamming errors (e.g. unimplemented GPU features.)
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.
@ -10,7 +10,7 @@ Messages are filtered in each class according to their severity, the filter will
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`:
Class names can be discovered from the log messages themselves. For example, this message is in the class `Service`:
```
[ 10.285042] Service <Error> core/hle/service/service.h:Service::Interface::SyncRequest:84: unknown/unimplemented function '0x01020000': port=APT:U
```