Changelog for libdwarf-devel-static-0.4.2-1.3.x86_64.rpm :

* Mon Oct 03 2022 Dirk Müller - update to 0.4.2:
* memory leak fixes
* How to deal with a dwarf_init
*() call that fails (DW_DLV_ERROR) in a simple way is finally documented in libdwarf.pdf and in the on-line html.
* Fri Jul 15 2022 Dirk Müller - update to 0.4.1:
* Two places where a carefully corrupted object file could result in libdwarf crashing a caller due to referencing memory outside the intended read area have been fixed (DW202205-001 and DW202206-001). One related to DW_FORM_ref_sig8, the other to the .debug_pubnames section.
* The library now accepts DW_AT_entry_pc in a CU DIE as a base address when DW_AT_low_pc is missing (an extension used by a current compiler).
* Added function dwarf_suppress_debuglink_crc() to allow callers to turn off doing a CRC calculation reading GNU debuglink data (saves time for library users accessing near-identical builds).- drop fix-CVE-2022-32200.patch (upstream)
* Tue Jun 07 2022 Dirk Müller - add fix-CVE-2022-32200.patch (bsc#1200291, CVE-2022-32200)
* Wed Apr 27 2022 Jan Engelhardt - Resolve rpmlint report \"libdwarf1.x86_64: E: shlib-policy-name-error SONAME: libdwarf.so.0, expected package suffix: 0\"
* Sun Apr 24 2022 Dirk Müller - update to 0.4.0:
* Removed the unused Dwarf_Error argument from dwarf_return_empty_pubnames() as the function can only return DW_DLV_OK. dwarf_xu_header_free() renamed to dwarf_dealloc_xu_header(). dwarf_gdbindex_free() renamed to dwarf_dealloc_gdbindex(). dwarf_loc_head_c_dealloc renamed to dwarf_dealloc_loc_head_c().
* dwarf_get_location_op_value_d() renamed to dwarf_get_location_op_value_c(), and 3 pointless arguments removed. The dwarf_get_location_op_value_d version and the three arguments were added for DWARF5 in libdwarf20210528 but the change was a mistake. Now reverted to the previous version.
* The .debug_names section interfaces have changed. Added dwarf_dnames_offsets() to provide details of facts useful in problems reading the section. dwarf_dnames_name() now does work and the interface was changed to make it easier to use.
* Mon Feb 21 2022 Dirk Müller - replace symlink by directory with hardlinks (bsc#1196198)
* Sun Feb 13 2022 Dirk Müller - update to 0.3.3:
* Release fixes a n assign offset = offset;
* Fixes a bug in LEB value reading of some values in the very rare case the compiler has emitted padding in the LEB
* Has improvements in detecting corrupt object files (Elf, MachO, and PE) and one new function that is only significant for those using an LLVM feature for Heterogenous Debugging. Passes Coverity Scan with zero issues.- drop libdwarf-gcc11.patch, libdwarf-gcc11-fixup.patch: upstream
* Wed Jun 16 2021 Fridrich Strba - Added patch:
* libdwarf-gcc11-fixup.patch + fix missing return and double define mistake in the upstream patch
* Tue Jun 15 2021 Dirk Müller - libdwarf-gcc11.patch: refresh with upstream patch
* Tue Jun 15 2021 Fridrich Strba - Added patch:
* libdwarf-gcc11.patch + skip correctly DW_FORM_implicit_const in _dwarf_formudata_internal (bsc#1187336)
* Fri Jun 11 2021 Fridrich Strba - update to 20210528: corrects libdwarf\'s handling of DWARF5 line table header DW_LNCT entries. Dwarfdump now prints DW_OP_bra and DW_OP_skip correctly and correctly validates the target of these operators. adds summary information on attribute/form-class uses and attribute/forms use to the existing option -ku summary on tags and attributes. Dwarfdump verifies many attribute references are usable and prints a little from the target DIE, including with DW_FORM_ref_sig8 references. Now dwarf.h shows many more extensions (added by compiler developers) to the TAGs and ATtributes defines. Alongide releases is a pdf, libdwarf2.1xl.pdf (xl.pdf as it is extra-large), that is the same as the latest libdwarf2.1.pdf but with the table-of-contents at the front, not the back, of the pdf. Created an experiment, it is around 15MB so seemed too large to place it in the release or to do multiple versions. Later updates will just replace it on prevanders.net.
* Wed Apr 21 2021 Wolfgang Frisch - Hardening: link as PIE (bsc#1185057).
* Fri Jan 29 2021 Dirk Müller - update to 20201201: dwarfdump now prints DWARF expression operators each on its own line. This makes viewing DWARF expressions much nicer given the increased use of much longer expressions. Those expression operators that reference DIES are now followed, verified, and the target DW_TAG and DW_AT_name are printed. A new dwarfdump.conf command \'option:\' lets one specify option: --format-expr-ops-joined in case you want the old style DWARF expression operators-on-one-line. Where the DWARF DIE children nest > nine-deep dwarfdump switches from indentation by spaces to a nest-level number.
* Mon Oct 26 2020 Dirk Mueller - update to 20201020:
* Fix various read and write outside bounds found via fuzzing
* Fri Sep 04 2020 Dirk Mueller - move libdwarf headers back to the old location
* Wed Sep 02 2020 Dirk Mueller - update to 20200825 (bsc#1142609, CVE-2019-14249) libdwarf now reads .debug_gnu_pubtypes & pubnames (non-standard but gcc creates them in DWARF5) via a small number of new functions and dwarfdump --print-debug-gnu prints both sections. Verifying the .debug_info offsets is not yet done. Dwarfdump now dumps DWARF5 .debug_rnglists and .debug_loclists. To handle DWARF5 there are a small number of new functions. All existing functions are still supported, but to read DWARF5 some small changes are required. In libdwarf see libdwarf2.1.pdf and also see dwarfdump now takes much less malloc() to work, as measured by valgrind --tool=massif and massif-visualizer. A dwarfdump run that did 2.2Gib of malloc/free before the changes now does 1.4GiB. libdwarf and dwarfdump now support DWARF5 .debug_rnglists. The new interfaces are documented in libdwarf/libdwarf2.1.pdf. The new option to dwarfdump is \"--print-raw-rnglists\". The code (dwarfdump/libdwarf), regressiontests, and readelfobj directories and all their tests are known to work on Linux(Ubuntu on x86_64 and i686), FreeBSD, MacOS Catalina (with Apple Command Line Tools), and IBM s390 (Big Endian!) running Ubuntu Linux. On Windows-MinGW the full regression tests have not been tested, but \'make check\' works for dwarfdump/libdwarf (the current dwarfdump make check actually does run dwarfdump and checks that dwarfdump basically works). Now a --disable-libelf configure/build of libdwarf/dwarfdump can read elf, mach-o DSYM, and PE executable/dll object files. Such a build will not need or use libelf or elf.h . The dwarfdump options that display Elf section headers or relocation record data are not available in a - -disable-libelf build. Nor is dwarfdump\'s support of reading archive files available in a --disable-libelf build. This libdwarf detects corrupt Elf object files much sooner than before, but does not explain what the corruption really is. Use GNU readelf (or readelfobj, a project on sourceforge) to get more detail about the problems found. See https://www.prevanders.net/dwarf.html for the git clone command for readelfobj. With --disable-libelf the --enable-dwarfgen option does not work: the dwarfgen build will fail. For building on machines without a usable elf.h or libelf but possibly with a libelf.h visible, --disable-libelf ensures the build won\'t use libelf or elf.h anywhere. - lz will be done if zlib.h is visible, independent of libelf, libelf.h, and elf.h If one has a standard Bourne shell (sh) available (such as sh on MacOS and sh in MinGW on Windows) one may be able to build libdwarf and dwarfdump natively and they can read Mach-o dSYM and PE object files to access DWARF information. This has NOT been tested under MacOS, so will likely fail on MacOS. No elf.h, libelf.h or zlib.h should be present. For example, the following is known to work under MinGW and this general plan applies to all builds including all builds with elf.h and libelf: mkdir test cd test [#](copy the source tree into test, if from git [#]the name of the top level will likely be \'code\') cd code The pre-build dwarf_names.[hc] and the tag related files are now part of the standard build so there is no longer any two-stage aspect of the build. The build simply compiles files in the distribution. If you use git to access the source be sure to sh scripts/FIX-CONFIGURE-TIMES to adjust the file timestamps as having timestamps in the right relationships is vital and git does not maintain timestamps. The script is always safe to run. It takes about 30 seconds. The complicated process of building certain .c and .h files has been relegated to the few people updating files libdwarf/libdwarf.h.in, libdwarf/dwarf_errmsg_list.h, dwarfdump/tag_attr_ext.list,dwarfdump/tag_attr.list, dwarfdump/tag_tree_ext.list, and dwarfdump/tag_tree.list. For everyone else the build is simply compiling the .c and .h files in the distribution. Simpler. sh scripts/buildstandardsource.sh creates these files. dwarfdump can now dump mach-o (MacOS) dSYM dwarf. All the usual libdwarf interfaces work. A new libdwarf initialization call dwarf_init_path() may be convenient for you to use.
* Fri Aug 02 2019 Martin Liška - Use FAT LTO objects in order to provide proper static library.
* Thu Feb 22 2018 p.drouandAATTgmail.com- Update to version 20180129 + Fixes libdwarf/dwarfdump vulnerabilities related to detecting corrupt DWARF and includes other small improvements- Changes from version 20170709 + Fixes a libdwarf vulnerability- Changes from version 20170416 + Begins to support the DWARF5 .debug_names section and other DWARF5 changes. (not tested, no test cases yet available). + Now supports DWARF5 split dwarf sensibly. The few new function interfaces can be ignored by those not needing split dwarf support. + The tools can now be built with cmake (the default build is still with configure)