-
Notifications
You must be signed in to change notification settings - Fork 129
[DRAFT] ProcessID, Signal, SignalSet, TaskInfo, ResourceUsageInfo #20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
milseman
wants to merge
12
commits into
apple:main
Choose a base branch
from
milseman:process_ego
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
ad80d0f
WIP: PID, and resource / task info
milseman 0ebaa29
Signal and SignalSet
milseman 544fc8a
TaskInfo and ResourceUsageInfo struct queries
milseman 881a8ad
Update Sources/System/Process/Signal.swift
milseman 0c32e4e
Update Sources/System/Process/Signal.swift
milseman c96a3e6
Update Sources/System/Process/Signal.swift
milseman a051d71
Update Sources/System/Process/Signal.swift
milseman 153e5d3
Update Sources/System/Process/Signal.swift
milseman e8b5ab4
Update Sources/System/Process/Signal.swift
milseman 9edaf16
Update Sources/System/Process/Signal.swift
milseman 5bc82a4
Update Sources/System/Process/Signal.swift
milseman 9830717
Update Sources/System/Process/Signal.swift
milseman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Update Sources/System/Process/Signal.swift
Co-authored-by: Karoy Lorentey <[email protected]>
- Loading branch information
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm, you can also get them on sockets...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh that's interesting. 🤔
Broken pipeis whatpsignalprints on SIGPIPE, which is why I suggested it. It has the advantage that it evokes the original name but also tries to clarify it a little.Should we use that, use
pipe, or should we try to find a more exact term?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, we imported
EPIPEasErrno.brokenPipe. I think we should probably use the same name here -- especially since it looks like the error is returned in the exact same situations as when the signal is sent.