public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/15827] Segfault on reading symbols from a fuzzed (corrupted) binary
Date: Wed, 16 Apr 2014 21:43:00 -0000	[thread overview]
Message-ID: <bug-15827-4717-yFspmTYLE0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15827-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
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  22869d73e127511e177a6bd855f9b5dbe22b9eca (commit)
      from  c4f87ca6dbe041e2a331e5054a76c9134f29d545 (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=22869d73e127511e177a6bd855f9b5dbe22b9eca

commit 22869d73e127511e177a6bd855f9b5dbe22b9eca
Author: Keith Seitz <keiths@redhat.com>
Date:   Wed Apr 16 14:39:10 2014 -0700

    PR gdb/15827

    Install some sanity checks that sibling DIE offsets are not beyond the
    defined limits of the DWARF input buffer in read_partial_die and
skip_one_die.

    2014-03-20  Keith Seitz  <keiths@redhat.com>

        PR gdb/15827
        * dwarf2read.c (skip_one_die): Check that all relative-offset
        sibling DIEs fall within range of the current reader's buffer.
        (read_partial_die): Likewise.

    2014-03-20  Keith Seitz  <keiths@redhat.com>

        PR gdb/15827
        * gdb.dwarf2/corrupt.c: New file.
        * gdb.dwarf2/corrupt.exp: New file.

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

Summary of changes:
 gdb/ChangeLog                        |    7 +++
 gdb/dwarf2read.c                     |    4 ++
 gdb/testsuite/ChangeLog              |    6 +++
 gdb/testsuite/gdb.dwarf2/corrupt.c   |   24 ++++++++++
 gdb/testsuite/gdb.dwarf2/corrupt.exp |   77 ++++++++++++++++++++++++++++++++++
 5 files changed, 118 insertions(+), 0 deletions(-)
 create mode 100644 gdb/testsuite/gdb.dwarf2/corrupt.c
 create mode 100644 gdb/testsuite/gdb.dwarf2/corrupt.exp

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


  parent reply	other threads:[~2014-04-16 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 13:05 [Bug cli/15827] New: " jutaky at gmail dot com
2014-03-21 16:51 ` [Bug gdb/15827] " keiths at redhat dot com
2014-04-16 21:43 ` cvs-commit at gcc dot gnu.org [this message]
2014-04-16 21:45 ` keiths at redhat dot com

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=bug-15827-4717-yFspmTYLE0@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).