bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/15140] AR produces invalid thin archive which cause binuti


From: cvs-commit at gcc dot gnu.org
Subject: [Bug binutils/15140] AR produces invalid thin archive which cause binutils to crash
Date: Fri, 15 Feb 2013 14:37:47 +0000

http://sourceware.org/bugzilla/show_bug.cgi?id=15140

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> 2013-02-15 14:37:47 UTC ---
CVSROOT:    /cvs/src
Module name:    src
Changes by:    address@hidden    2013-02-15 14:37:39

Modified files:
    binutils       : ChangeLog readelf.c ar.c elfcomm.c 
    bfd            : ChangeLog archive.c 
    binutils/doc   : binutils.texi 

Log message:
    PR binutils/15140
    * ar.c (open_inarch): Fail on attempts to convert a normal archive
    to a thin archive or vice versa.
    * elfcomm.c (make_qualified_name): Handle corrupted thin
    archives.
    * readelf.c (process_archive): Likewise.
    * doc/binutils.texi: Clarify documentation describing thin
    archives.

    * archive.c (_bfd_get_elt_at_filepos): Prevent an infinite loop
    accessing a corrupt nested archive.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/binutils/ChangeLog.diff?cvsroot=src&r1=1.1990&r2=1.1991
http://sourceware.org/cgi-bin/cvsweb.cgi/src/binutils/readelf.c.diff?cvsroot=src&r1=1.594&r2=1.595
http://sourceware.org/cgi-bin/cvsweb.cgi/src/binutils/ar.c.diff?cvsroot=src&r1=1.86&r2=1.87
http://sourceware.org/cgi-bin/cvsweb.cgi/src/binutils/elfcomm.c.diff?cvsroot=src&r1=1.4&r2=1.5
http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/ChangeLog.diff?cvsroot=src&r1=1.5966&r2=1.5967
http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/archive.c.diff?cvsroot=src&r1=1.95&r2=1.96
http://sourceware.org/cgi-bin/cvsweb.cgi/src/binutils/doc/binutils.texi.diff?cvsroot=src&r1=1.197&r2=1.198

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- 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]