public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb/gdb-7.11-branch] Remove gdb/python/python.c code that handles strlen failing with -1
Date: Tue, 03 May 2016 11:46:00 -0000 [thread overview]
Message-ID: <aaa3178dfb979f8ec476a326aca273125a1e3ee9@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT aaa3178dfb979f8ec476a326aca273125a1e3ee9 ***
Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.11-branch
Commit: aaa3178dfb979f8ec476a326aca273125a1e3ee9
Remove gdb/python/python.c code that handles strlen failing with -1
This makes no sense -- strlen doesn't really ever fail with -1.
gdb/ChangeLog:
2016-05-03 Pedro Alves <palves@redhat.com>
* python/python.c (_initialize_python) [IS_PY3K]: Remove dead
code.
next reply other threads:[~2016-05-03 11:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 11:46 sergiodj+buildbot [this message]
2016-05-03 11:47 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-03 13:08 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-05-03 13:21 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-03 13:25 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-05-03 13:32 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-05-03 13:40 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-05-03 14:13 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-05-03 18:09 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-05-03 19:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-03 19:32 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
2016-05-04 0:08 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-05-04 0:28 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-05-04 0:51 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-04 1:23 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-05-04 2:10 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-04 2:34 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-04 3:11 ` Failures on Fedora-ppc64le-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=aaa3178dfb979f8ec476a326aca273125a1e3ee9@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--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).