From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: Prepare for 0.175
Date: Wed, 14 Nov 2018 12:18:00 -0000 [thread overview]
Message-ID: <1542197796-10130-1-git-send-email-mark@klomp.org> (raw)
Set version to 0.175
Update NEWS and elfutils.spec.in.
Regenerate po/*.po files.
Signed-off-by: Mark Wielaard <mark@klomp.org>
---
NEWS | 18 +
config/elfutils.spec.in | 14 +
configure.ac | 2 +-
po/de.po | 1162 ++++++++++++++++++++++++----------------------
po/es.po | 1169 ++++++++++++++++++++++++----------------------
po/ja.po | 1166 ++++++++++++++++++++++++----------------------
po/pl.po | 1172 ++++++++++++++++++++++++----------------------
po/uk.po | 1175 +++++++++++++++++++++++++----------------------
8 files changed, 3113 insertions(+), 2765 deletions(-)
diff --git a/NEWS b/NEWS
index 0b7994e..95fbac0 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,21 @@
+Version 0.175
+
+readelf: Handle mutliple .debug_macro sections.
+ Recognize and parse GNU Property notes, NT_VERSION notes
+ and GNU Build Attribute ELF Notes.
+
+strip: Handle SHT_GROUP correctly.
+ Add strip --reloc-debug-sections-only option.
+ Handle relocations against GNU compressed sections.
+
+libdwelf: New function dwelf_elf_begin.
+
+libcpu: Recognize bpf jump variants BPF_JLT, BPF_JLE, BPF_JSLT and BPF_JSLE.
+
+backends: RISCV handles ADD/SUB relocations. Handle SHT_X86_64_UNWIND.
+
+Fixes CVE-2018-18310, CVE-2018-18520 and CVE-2018-18521.
+
Version 0.174
libelf, libdw and all tools now handle extended shnum and shstrndx correctly.
diff --git a/config/elfutils.spec.in b/config/elfutils.spec.in
index 0f9687d..e2fb0e4 100644
--- a/config/elfutils.spec.in
+++ b/config/elfutils.spec.in
@@ -227,6 +227,20 @@ rm -rf ${RPM_BUILD_ROOT}
%{_sysctldir}/10-default-yama-scope.conf
%changelog
+* Wed Nov 14 2018 Mark Wielaard <mark@klomp.org> 0.175-1
+- readelf: Handle mutliple .debug_macro sections.
+ Recognize and parse GNU Property notes, NT_VERSION notes and
+ GNU Build Attribute ELF Notes.
+- strip: Handle SHT_GROUP correctly.
+ Add strip --reloc-debug-sections-only option.
+ Handle relocations against GNU compressed sections.
+- libdwelf: New function dwelf_elf_begin.
+- libcpu: Recognize bpf jump variants BPF_JLT, BPF_JLE, BPF_JSLT
+ and BPF_JSLE.
+- backends: RISCV handles ADD/SUB relocations.
+ Handle SHT_X86_64_UNWIND.
+- Fixes CVE-2018-18310, CVE-2018-18520 and CVE-2018-18521.
+
* Fri Sep 14 2018 Mark Wielaard <mark@klomp> 0.174-1
- libelf, libdw and all tools now handle extended shnum and shstrndx
correctly.
diff --git a/configure.ac b/configure.ac
index da9f8cb..b89b867 100644
--- a/configure.ac
+++ b/configure.ac
@@ -17,7 +17,7 @@ dnl GNU General Public License for more details.
dnl
dnl You should have received a copy of the GNU General Public License
dnl along with this program. If not, see <http://www.gnu.org/licenses/>.
-AC_INIT([elfutils],[0.174],[https://sourceware.org/bugzilla],[elfutils],[http://elfutils.org/])
+AC_INIT([elfutils],[0.175],[https://sourceware.org/bugzilla],[elfutils],[http://elfutils.org/])
dnl Workaround for older autoconf < 2.64
m4_ifndef([AC_PACKAGE_URL],
next reply other threads:[~2018-11-14 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 12:18 Mark Wielaard [this message]
2018-11-15 7:54 ` Martin Liška
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1542197796-10130-1-git-send-email-mark@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).