public inbox for src-cvs@sourceware.org
help / color / mirror / Atom feed
From: willnewton@sourceware.org
To: src-cvs@sourceware.org
Subject: gdb and binutils branch master updated. b9502d3fd7848cd4d843be8bdc28633a3d24438d
Date: Wed, 06 Nov 2013 15:15:00 -0000	[thread overview]
Message-ID: <20131106151545.11390.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  b9502d3fd7848cd4d843be8bdc28633a3d24438d (commit)
      from  452a569eff947a21369d43cc7632c320e5b8a085 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

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

commit b9502d3fd7848cd4d843be8bdc28633a3d24438d
Author: Will Newton <will.newton@linaro.org>
Date:   Fri Nov 1 14:14:50 2013 -0700

    gdb/dwarf2read.c: Sanity check DW_AT_sibling values.
    
    When reading objects with corrupt debug information it is possible that
    the sibling chain can form a loop, which leads to an infinite loop and
    memory exhaustion.
    
    Avoid this situation by disregarding and DW_AT_sibling values that point
    to a lower address than the current entry.
    
    gdb/ChangeLog:
    
    2013-11-06  Will Newton  <will.newton@linaro.org>
    
    	PR gdb/12866
    	* dwarf2read.c (skip_one_die): Sanity check DW_AT_sibling
    	values.  (read_partial_die): Likewise.

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog    |    6 ++++++
 gdb/dwarf2read.c |   22 ++++++++++++++++++++--
 2 files changed, 26 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gdb and binutils


                 reply	other threads:[~2013-11-06 15:15 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=20131106151545.11390.qmail@sourceware.org \
    --to=willnewton@sourceware.org \
    --cc=src-cvs@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).