[kernel] Fix kernel sys_signal handling on multi-code segment executables #2113
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Should fix "SIGNAL sys_signal supplied handler is bad" from #1443 (comment).
The kernel was not properly accepting signal handlers from executables that had multiple code segments - medium model IA16 or OWC large/medium model executables.
Tested on QEMU for large model OWC executables, but not for multi-code segment large model OWC, which C86 appears to be. @rafael2k, if the message disappears, then the problem is fixed and signal handling should work as expected.