Capture standard out and standard error for xbmc #54
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
That way we log exceptions when xbmc reboots, so we actually have a clue whhat assertion or exception was thrown. logged to /root/.xbmc/temp/xbmcstart.log
|
when I crash, I get an error code which useless. what are other examples of useful info that might be captured. One other concern is filling the disk as xbmc will be restarted again and again if it keeps crashing. |
|
http://www.pivosforums.com/viewtopic.php?f=25&t=2554&start=200#p26515 for one. Also get stack dumps out of xbmc when get errors for jump to unknown location and other errors during bad video playback. Will go back and reproduce that so I can show you the output from that. The disk filling up due to disk thrashing on infinite crashes would be a problem but seems like a symptom of a bigger problem. Should there be some kind of sanity limiter on the until loop that after a certain amount of tries that it gives up and stops trying? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This way we log exceptions when xbmc restarts, so we actually have a clue what assertion or exception was thrown. Makes it much easier to find reason for segfaults because can actually see log for the segfault.
logged to /root/.xbmc/temp/xbmcstart.log and xbmcstart.old.log