Add file operation logging to the host app - #35
Open
nextgeniuspro wants to merge 1 commit into
Open
nextgeniuspro wants to merge 1 commit into
nextgeniuspro wants to merge 1 commit into
Conversation
This file contains hidden or 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
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 is proposal to add verbose logs from host application so that developer may track in the console all file operations that dreamcast app do. This might be useful for the case when developer want to check, for instance, that when he load a level, all resources of that level were loaded in ram at loading stage and no other file reading operation will occure later, so that he can start music streaming which will not be interruped.
Usage is pretty simple, new command line argument
-vafter which comma-separated list of needed operation is expected. Example:This PR adds logs to all operations that host apps provides, except communication for debugger.
Also, as additional fix was added potential crash of using closed directory, like calling twice closedir for the same directory. While in practice it would be hard to reproduce it still better to have such fix