fix(osx): consolidate error checks in alt_clock_gettime
for clarity
#4803
+11
−3
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.
Summary
Fixes an issue in
alt_clock_gettime()
where the return value ofhost_get_clock_service()
andclock_get_time()
was not checked. This could lead to undefined behavior or crashes on macOS if the system call fails.Problem
The original implementation assumes
host_get_clock_service()
andclock_get_time()
always succeed:However, these system calls can fail under certain conditions (e.g., lack of privileges or system resource issues). Without checking their return values, the subsequent use of uninitialized
mts
can lead to undefined behavior.Fix
This PR introduces proper error handling:
host_get_clock_service()
clock_get_time()
-1
on failure, consistent with typical POSIX time functionsChanges
host_get_clock_service()
andclock_get_time()
inalt_clock_gettime()
mach_port_deallocate()
is always called afterhost_get_clock_service()
Platforms Affected
alt_clock_gettime()
Testing
Related Issues
N/A — this is a proactive fix identified during code audit
Checklist