aboutsummaryrefslogtreecommitdiff
path: root/ld/NEWS
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2022-05-03 11:42:24 +0100
committerNick Clifton <nickc@redhat.com>2022-05-03 11:42:24 +0100
commitba951afb99912da01a6e8434126b8fac7aa75107 (patch)
treee94ddfba29d29a82ab36d28592d6c8e7edd04350 /ld/NEWS
parent46465574a925062ba7dfa72f49ba5199d7a39fc3 (diff)
downloadgdb-ba951afb99912da01a6e8434126b8fac7aa75107.zip
gdb-ba951afb99912da01a6e8434126b8fac7aa75107.tar.gz
gdb-ba951afb99912da01a6e8434126b8fac7aa75107.tar.bz2
Add a linker warning when creating potentially dangerous executable segments. Add tests, options to disabke and configure switches to choose defaults.
Diffstat (limited to 'ld/NEWS')
-rw-r--r--ld/NEWS24
1 files changed, 23 insertions, 1 deletions
diff --git a/ld/NEWS b/ld/NEWS
index b845531..514d1d9 100644
--- a/ld/NEWS
+++ b/ld/NEWS
@@ -1,6 +1,6 @@
-*- text -*-
-* The linker will now generate a warning message if the stack is made
+* The ELF linker will now generate a warning message if the stack is made
executable. By default this warning is not issued if the user has
specifically requested an executable stack via the "-z execstack"
command line option, but the warning can be forced via the new
@@ -8,6 +8,28 @@
an executable stack can be suppressed via the "--no-warn-execstack"
option.
+ In addition the ELF linker will also warn if it creates a memory resident
+ segment with all three of the Read, Write and eXecute permissions set, or
+ if it creates a thread local data segment with the eXecute permission set.
+ These warnings can be disabled via --no-warn-rwx-segments option and
+ re-enabled via the --warn-rwx-segments option.
+
+ New configure options can also control these new features:
+
+ --enable-warn-execstack=no
+ will disable the warnings about creating an executable stack.
+
+ --enable-warn-execstack=yes
+ will make --warn-execstack enabled by default.
+
+ --enable-warn-rwx-segments=no
+ will make --no-warn-rwx-segments enabled by default.
+
+ --enable-defaul-execstack=no
+ will stop the creation of an executable stack simply because an input file
+ is missing a .note.GNU-stack section, even on architectures where this
+ ehaviour is the default.
+
* TYPE=<type> is now supported in an output section description to set the
section type value.