website: Mention that these numbers are ONLY for 32-bit x86 #3
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
See https://fedora.juszkiewicz.com.pl/syscalls.html for the fact that other arches have completely different syscall numbers, including x86_64, where e.g. read() is 0, not 3. This confusion actually resulted in one of my prototype programs being wrong :)
nh2
added a commit
to nh2/hatrace
that referenced
this pull request
Feb 17, 2019
What we had so far was for 32-bit x86 only. Fixed where we got the info from via gregose/syscall-table#3.
|
^. There exist x64 specific obstructions enhancing possibilities dramatically, and not in terms of maths |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
See https://fedora.juszkiewicz.com.pl/syscalls.html for the fact that other arches
have completely different syscall numbers, including x86_64, where e.g.
read() is 0, not 3.
This confusion actually resulted in one of my prototype programs being wrong :)