From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, Jakub Jelinek <jakub@redhat.com>,
Mark Wielaard <mark@klomp.org>, Martin Liska <mliska@suse.cz>
Subject: DWZ 0.13 released
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <9fe97d8e-c6fb-5fc8-328f-9278293c9176@suse.de> (raw)
Hi,
DWZ 0.13 has been released.
There is a web page for DWZ at:
https://sourceware.org/dwz/
DWZ 0.13 includes the following changes and enhancements:
* DW_OP_GNU_variable_value support.
* A multifile with only a .debug_str section is now allowed. Previously
this resulted in an error "dwz: <multifile>: .debug_info section not
present".
* Improved handling of unordered section header table. Previously this
resulted in an error "dwz: Section offsets in <file> not monotonically
increasing".
* Improved handling of NOBITS sections generated by objcopy
--only-keep-debug. Previously this resulted in an error "dwz:
Allocatable section in <file> after non-allocatable ones".
* Sections .debug_gnu_names and .debug_gnu_types are now handled, by
removing them from the output file (similar to what is done for
sections .debug_names and .debug_types). Previously this resulted in
an error "dwz: Unknown debugging section <section>".
* A case where previously the error "dwz: Error mmapping multi-file
temporary files" was generated, now is handled by generating the error
"dwz: No suitable DWARF found for multifile optimization".
* A case where previously the error "dwz: DWARF version 0 unhandled"
was generated, is now handled by generating the error "dwz: Found
compressed .debug_info section, not attempting dwz compression".
* Fixed multifile mode exit status to behave the same as non-multifile
mode exit status.
* When running into "dwz:<file>: .debug_info section not present" , dwz
now exits with 0.
* The following assertion failures were fixed:
- dwz.c:2363: checksum_die: Assertion `
((!op_multifile && !rd_multifile && !fi_multifile)
|| cu != die_cu (ref))
&& (!op_multifile || cu->cu_chunk == die_cu (ref)->cu_chunk)
' failed.
- dwz: dwz.c:8558: adjust_exprloc: Assertion `
refd != NULL && !refd->die_remove
' failed.
- dwz: dwz.c:1722: read_loclist: Assertion `
ptr + len <= endsec
' failed.
- dwz: dwz.c:9068: write_die: Assertion `
p && (form == DW_FORM_sec_offset || form == DW_FORM_data4)
' failed
- dwz: dwz.c:9901: read_dwarf: Assertion `
data != NULL && data->d_buf != NULL
' failed
* A testsuite was added.
Thanks,
- Tom
reply other threads:[~2019-08-02 10:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9fe97d8e-c6fb-5fc8-328f-9278293c9176@suse.de \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.com \
--cc=mark@klomp.org \
--cc=mliska@suse.cz \
/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).