[Debug] Add debugging support for timestamps in socket communication (optional) #371
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.
📝 Description
This PR introduces a
DebugTimeInfofunction to log timestamped messages for key socket communication operations. This update enhances the ability to monitor and debug the timing of network communication operations.Details:
The following updates were made:
New Method Added:
DebugTimeInfowas added to print debug messages with timestamps in a human-readable format. It is guarded by theCO_SIM_IO_TIMESTAMP_DEBUGpreprocessor flag, ensuring the feature can be enabled or disabled as needed.Time Debug Logs: The
DebugTimeInfofunction was integrated into various methods likeConnectDetail,DisconnectDetail,SendString,ReceiveString,SendDataContainer,ReceiveDataContainer,SendSize, andReceiveSizeto log timestamps before and after important communication steps.Chrono Header: The
chrono,ctime, andiomanipheaders were included to handle time formatting and timestamp generation. Only when required.🆕 Changelog
Commits:
Patch breakdown:
DebugTimeInfofunction.DebugTimeInfofunction.chronoand time formatting utilities to capture and display time.