public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] readelf: handle corrupted chains better
Date: Tue, 24 Feb 2015 16:18:00 -0000	[thread overview]
Message-ID: <94d15024fe3dff908ab570aaa741b1c834c856d6@kwanyin> (raw)

*** TEST RESULTS FOR COMMIT 94d15024fe3dff908ab570aaa741b1c834c856d6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 94d15024fe3dff908ab570aaa741b1c834c856d6

readelf: handle corrupted chains better
The current chain walker tries to protect itself against loops, by only
works with loops of length 1: a chain that points to itself.  If you have
a chain longer than that (3->4->3->4->...), readelf will still hang.

Since we know the max length of the chain, simply abort when we've walked
more times than that.  The only way that could have happened is if there
was a loop.


             reply	other threads:[~2015-02-24 16:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 16:18 sergiodj+buildbot [this message]
2015-02-24 16:23 ` Failures on Fedora-ppc64be-m64, branch master sergiodj+buildbot
2015-02-24 16:29 ` Failures on Debian-i686, " sergiodj+buildbot
2015-02-24 17:01 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2015-02-24 17:14 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2015-02-24 17:45 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-02-24 18:25 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-02-24 18:37 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2015-02-24 19:55 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-02-24 20:05 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2015-02-24 21:05 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot

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=94d15024fe3dff908ab570aaa741b1c834c856d6@kwanyin \
    --to=sergiodj+buildbot@redhat.com \
    --cc=gdb-testers@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).