This event is triggered when the toxcore library logs an internal message. This is mostly useful for debugging. This callback can be called from any function, not just Tox.iterate. This means the user data lifetime must at least extend between registering and unregistering it or tox_kill.
Other toxcore modules such as toxav may concurrently call this callback at any time. Thus, user code must make sure it is equipped to handle concurrent execution, e.g. by employing appropriate mutex locking.
| level |
The severity of the log message. |
| file |
The source file from which the message originated. |
| line |
The source line from which the message originated. |
| func |
The function from which the message originated. |
| message |
The log message. |