For strange reasons which made sense at the time, the text segment was
authorderaadt <deraadt@openbsd.org>
Wed, 20 Dec 2023 14:50:08 +0000 (14:50 +0000)
committerderaadt <deraadt@openbsd.org>
Wed, 20 Dec 2023 14:50:08 +0000 (14:50 +0000)
commit805b87ea74e0d6b0f6f35a146ae727de198ab801
tree335d80c56e3db5aa3787d33806c2e229988bc498
parentbd1f785c28f4b4197a47ba70a9ca93c3c4e0cc47
For strange reasons which made sense at the time, the text segment was
placed head of the btext (boot.text) segment.  (the boot.text segment is
"unmapped" after initization, as a self-protection mechanism).  this meant
the LOAD's virtual addresses were not in sequence, which clearly isn't
what we intended.
12 files changed:
libexec/ld.so/aarch64/ld.script
libexec/ld.so/alpha/ld.script
libexec/ld.so/amd64/ld.script
libexec/ld.so/arm/ld.script
libexec/ld.so/hppa/ld.script
libexec/ld.so/i386/ld.script
libexec/ld.so/m88k/ld.script
libexec/ld.so/mips64/ld.script
libexec/ld.so/powerpc/ld.script
libexec/ld.so/riscv64/ld.script
libexec/ld.so/sh/ld.script
libexec/ld.so/sparc64/ld.script