Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: yao@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [patch] Move common macros to i386-common.h
Date: Mon, 28 Feb 2011 18:12:00 -0000	[thread overview]
Message-ID: <m3pqqc81yf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201102232117.p1NLHdhA015543@glazunov.sibelius.xs4all.nl> (Mark	Kettenis's message of "Wed, 23 Feb 2011 22:17:39 +0100 (CET)")

>>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:

Mark> I'm particularly worried about changes I'll make myself.  My primary
Mark> development platform is OpenBSD which isn't supported by gdbserver.
Mark> So I won't be building the gdbserver code, so I won't notice any
Mark> problems my diffs (and other people's diffs) will introduce in
Mark> gdbserver.

I agree this is a potential problem, but it does not worry me very much.

First, I think that we already just make a best effort not to break GDB
on hosts that do not have active GDB developers.

Second, for active hosts, breakage is noticed and fixed quickly.

Third, we're looking at setting up a buildbot for GDB.  See:

    http://sourceware.org/gdb/wiki/BuildBot

We're still discussing the various options, but one idea is to host it
on the GCC Compile Farm, plus let people host their own buildslaves.

Tom


  parent reply	other threads:[~2011-02-28 18:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-13  9:58 Yao Qi
2011-02-13 13:40 ` Mark Kettenis
2011-02-17  6:36   ` Yao Qi
2011-02-17  6:41     ` Joel Brobecker
2011-02-17 18:15       ` Jan Kratochvil
2011-02-23  5:36   ` Yao Qi
2011-02-23 21:35     ` Mark Kettenis
2011-02-24  4:32       ` Yao Qi
2011-02-24  5:11       ` Joel Brobecker
2011-02-28 18:12       ` Tom Tromey [this message]
2011-03-11  6:39 ` [try 2nd, patch] Move common macros to i386-dbg-reg.h Yao Qi
2011-03-29  7:54   ` Yao Qi
2011-04-07 14:07     ` Yao Qi
2011-04-07 15:54       ` Mark Kettenis
2011-04-11  2:01         ` Yao Qi
2011-04-13 17:05           ` Joel Brobecker
2011-04-13 18:48             ` Jan Kratochvil
2011-04-14  8:05             ` Yao Qi
2011-04-25 11:03             ` Yao Qi

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=m3pqqc81yf.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=yao@codesourcery.com \
    /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