XBMC Logging
#1
I have seen this done pretty much everywhere where you have to set setting to enable detail logging. ie debug logs.

Why not log everything to memory and then output to a file when we have exit the program or when the program crashes ?

The only side effect is that memory taken by the log will get bigger which perhaps we can handle by flushing log to disk when app is idling.

This should eliminate request for debug logs.
The normal XBMC log IS NOT a debug log, to enable debug logging you must toggle it on under XBMC Settings - System or in advancedsettings.xml. Use XBMC Debug Log Addon to retrieve it.
Reply
#2
CrashX Wrote:I have seen this done pretty much everywhere where you have to set setting to enable detail logging. ie debug logs.

Why not all log everything to memory and then output to a file when we have exit the program or when the program crashes ?

The only side effect is that memory taken by the log will get bigger which perhaps we can handle by flushing log to disk when app is idling.

This should eliminate request for debug logs.

what happens when the app crashes ?
Reply
#3
davilla Wrote:what happens when the app crashes ?

We trap it and dump log information to a file. We do something similar today with dmp files.
The normal XBMC log IS NOT a debug log, to enable debug logging you must toggle it on under XBMC Settings - System or in advancedsettings.xml. Use XBMC Debug Log Addon to retrieve it.
Reply

Logout Mark Read Team Forum Stats Members Help
XBMC Logging0