Repository navigation
0.30.1: the System V row states its program headers (no PT_PHDR), found on a System V kernel - #38
Merged
Merged
Conversation
The kernel of AT&T UNIX System V/386 Release 4.0 refuses an executable that has a PT_PHDR entry and no PT_INTERP one (elfexec), after the old image is gone, so a program of i686-svr4-musl was killed as it started. A static lld link writes PT_PHDR unless the headers are stated; link/svr4.ld states them: the three segments the link made before, the file's headers in the first, no PT_PHDR. The emulation (ibcs-us) accepts either form, so CI now reads the headers of the built program. Measured on that kernel (Release 4.0 Version 3.0 in QEMU, locally, once): the specification's suite 111 held / 0 did not hold; the program of checks/svr4 in both modes; no member changes.
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
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.
What
i686-svr4-musllinks with a linker script,link/svr4.ld, that states the program headers: the same threePT_LOADsegments the link made before (the file's headers inside the first),PT_GNU_EH_FRAME,PT_GNU_STACK, and noPT_PHDR. No member changes; version 0.30.1.Why
The row's programs were run on a System V kernel for the first time: AT&T UNIX System V/386 Release 4.0 Version 3.0, installed in QEMU from its floppy set (media this platform neither holds nor distributes), on the developer's machine.
Every program was killed as it started (status 137). The kernel's
elfexecrefuses an executable that has aPT_PHDRentry and noPT_INTERPone — the entry is for the run-time linker — and it refuses after the old image is gone. A static lld link always writesPT_PHDRwhen the headers are loaded. ibcs-us accepts either form, which is why the emulation never showed it.Measured
With this branch's link, nothing rewritten after it:
env,time,fs,terminal)checks/svr4, dev (stripped of debugging sections to fit a floppy) and release (as linked)CI cannot run on that kernel; the
svr4job now reads the built program's headers (noPT_PHDR/PT_INTERP, threePT_LOAD).Not in this change
The run on the System V kernel is not automated: no package of its media exists.