bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/21994] Hang in process_version_sections with ent.vd_next =


From: cvs-commit at gcc dot gnu.org
Subject: [Bug binutils/21994] Hang in process_version_sections with ent.vd_next = 0 and aux.vda_next = 0
Date: Tue, 05 Sep 2017 14:33:26 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=21994

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The binutils-2_29-branch branch has been updated by Nick Clifton
<address@hidden>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=64aa1246572306b72dc479b46d13ff749b0c3236

commit 64aa1246572306b72dc479b46d13ff749b0c3236
Author: Nick Clifton <address@hidden>
Date:   Tue Sep 5 15:32:04 2017 +0100

    Import patches from mainline to fix minor binutils bugs:

        PR 21861
        * winduni.c (codepages): Use cp1252 for codepage 0.

        PR 21813
        * rddbg.c (read_symbol_stabs_debugging_info): Check for an empty
        string whilst concatenating symbol names.

        PR 21909
        * prdbg.c (pr_int_type): Increase size of local string buffer.
        (pr_float_type): Likewise.
        (pr_bool_type): Likewise.

        PR 21820
        * readelf.c (dump_section_as_strings): Do not fail if the section
        was empty.
        (dump_section_as_bytes): Likewise.

        PR 21990
        * readelf.c (process_version_sections <SHT_GNU_verneed>): Check
        for invalid vn_next field before adding to idx.  Use unsigned
        long for index vars.  Move index checks.
        <SHT_GNU_verdef>: Likewise for vd_next.

        PR 21994
        * readelf.c (process_version_sections <SHT_GNU_verdef>): Check
        vd_aux and vda_next for sanity.  Delete "end".  Correct overflow
        checks.
        (process_version_sections <SHT_GNU_verneed>): Correct overflow
        check.  Don't report invalid vna_next on overflow.  Do report
        invalid vna_next on size less than aux info.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]