Opened 9 years ago
Last modified 7 years ago
#3339 closed enhancement
Command line option for pid+timestamp in OOS-log filename — at Initial Version
Reported by: | elexis | Owned by: | |
---|---|---|---|
Priority: | Nice to Have | Milestone: | Alpha 23 |
Component: | Core engine | Keywords: | patch |
Cc: | Patch: |
Description
If you try to reproduce an out-of-sync error, host a game with one instance, join as a client with the second instance of 0ad and actually manage to produce an out of sync error, then both instances of 0ad will write the ooslog to the same file. Thus one file will be overwritten and you can't diff the files.
attachment:t3255_use_timestamp_and_pid_for_oosdump_filename.patch:ticket:3255 contains a patch that adds the current unix timestamp and process id to the filename and thereby prevents the file from being overwritten.
TODO: However since oos dumps are very big (dozens of megabytes) multiple files should only be created if the application was started with a specific command line argument.
Change History (1)
by , 9 years ago
Attachment: | t3339_command_line_option_ooslog_unique_v1.patch added |
---|
Adds the command line switch, updates readme.txt. Add
true ||
to thecit->second != expected
check in line 647 ofNetTurnManager
to trigger an out of sync error, even as the only client on a server.