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] Remove gdb.base/coremaker2.c
Date: Thu, 17 Dec 2015 06:35:00 -0000	[thread overview]
Message-ID: <f1637ebed142eabd96cbc009edda8ec903c71fd6@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT f1637ebed142eabd96cbc009edda8ec903c71fd6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f1637ebed142eabd96cbc009edda8ec903c71fd6

Remove gdb.base/coremaker2.c

I happen to find that coremaker2.c isn't used in the testsuite (if I
don't miss anything).  I don't believe it until I see this ChangeLog
entry,

1999-11-18  Fred Fish  <fnf@cygnus.com>

        * gdb.base/coremaker2.c: Add sample program for generating
        cores that is more self contained than coremaker.c.  Eventually
        I'll add more code to this and tie it into the testsuite.

looks Fred didn't "tie it into testsuite" later.

gdb/testsuite:

2015-12-11  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/coremaker2.c: Remove.


             reply	other threads:[~2015-12-17  6:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17  6:35 sergiodj+buildbot [this message]
2015-12-17  6:35 ` Failures on Debian-s390x-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  6:51 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-17  6:52 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-12-17  7:00 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2015-12-17  7:08 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2015-12-17  7:13 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2015-12-17  7:16 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-12-17  7:22 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2015-12-17 10:19 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2015-12-17 15:11 ` Failures on Debian-i686, " sergiodj+buildbot
2015-12-17 15:31 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-12-17 15:59 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-12-17 21:14 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-12-17 21:32 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-18  0:32 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-18  1:07 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2015-12-18  1:23 ` Failures on Fedora-ppc64le-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=f1637ebed142eabd96cbc009edda8ec903c71fd6@gdb-build \
    --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).