| Age | Commit message (Collapse) | Author |
|---|
|
Gives us working objcopy, objdump, etc, and the ability to process core files
to some extent.
ok and pushed upstream kettenis@
|
|
remove testsuites (not useable) remove mmalloc (not part of new binutils).
|
|
|
|
|
|
RODATA_* align macros to preserve current behavior on other
archs and allow for 1G sep between beginning of exe and beginning of data
DARPA funded work.
|
|
|
|
of putting it with the text. This removes the execute permission
from readonly data. This constrains the executable region to portions
of the executable which need to be executable. Note: not all processors
or mmus are capable of -X protection at the page level, but should
handle ELF images which specify specific RWX protections on each section.
|
|
|
|
executable regions which are writable. If a section of an executable is
writable and executable, it is much easier for errant code to modify the
executable's behavior.
Two current areas in shared library environments which have this
critical problem are the GOT (Global Offset Table) and PLT (Procedure
Linkage Table). The PLT is required to be executable and both GOT and
PLT are writable on most architectures. On most ELF architecture
machines this would cause shared libraries to have data and BSS marked
as executable.
Padding to the linker script for programs and shared libraries/objects
to isolate the GOT and PLT into their own load sections in the
executables. This allows only the text(readonly) region and the PLT
region to be marked executable with the normal data and BSS not marked
as executable. The PLT region is still marked executable on most
architectures because the PLT lives in the "data" or "BSS" regions
and the dynamic loader will need to modify it. Since the GOT and PLT
should only ever be written by the dynamic linker, it will be modified
to mprotect those regions so that they are not writable during normal
execution. If the dynamic linker needs to modify the regions later,
(eg for lazy binding), it will mprotect the region, make the necessary
changes, and mprotect it back. Since it is possible to receive a
signal which would interrupt the program flow and perhaps cause the
dynamic linker to modify the same (or nearby) PLT references, it is now
necessary for signals to be blocked for the duration of the mprotect.
|
|
|
|
XXX - we might want to improve the version selection logic when feeding
those diffs back to FSF, but we can't do that until we bump our version
to OpenBSD 3.2 because then the tree wouldn't build.
|
|
PR/2822. Submited to binutils as well.
|
|
|
|
|
|
only in the generated files).
- Regen.
Whenever is possible, changes should be done to the source files (.am, .in).
That way is easier to track and merge local changes when importing.
|
|
|
|
|
|
- only the binutils package (no gdb here)
- don't import libiberty and texinfo, they are elsewhere
- remove all .info* generated files
|
|
Fixes this for lex and binutils' bfd.
Also, do not install ansidecl.h, we don't really need it, bfd.h uses it,
and we installed it so that bfd worked, so let bfd.h include it directly.
prompted by mickey@
|
|
via pr 2447; deraadt@ ok.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
of a program is done...
|
|
bug-fixes...
|
|
the way Red hat choose. Both ways work, the important thing is that
things match. However if we use the red hat solution we will not need
to merge local changes when importing new binutils releases; espie made
me aware of the import issues which I forgot due to lack of sleep :-).
|
|
match the maxpagesize between bfd and ld.
|
|
|
|
|
|
|
|
but we have a mix here -> convert the old ones to heed DESTDIR.
Also, fix manpages installation in Makefile.bsd-wrapper
(INSTALL_MAN setting that got lost, bad MANDIR, don't set MANDIR if
PREFIX is the standard location)
|
|
(This is probably a work-around for a bug in ksh)
|
|
|
|
(trivial part done, `interesting' patches remain)
|
|
|
|
- only the binutils package (no gdb here)
- don't import libiberty and texinfo, they are elsewhere
- remove all .info* generated files
|
|
|
|
so that make install will heed DESTDIR, and so gdb.info & friends
will finally show up in distrib/sets...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
on - this way now the whole tree builds without requiring any file
being executable (binutils was the last which required it) - now
ctm -> cvs checkout -> make build works just fine (aside from
other bugs in the source tree :-)
|
