Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Doug Evans <dje@google.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Crazy?
Date: Thu, 18 Jun 2015 01:21:00 -0000	[thread overview]
Message-ID: <9F4CA95A-E896-4B86-9037-C3C14D21FEC5@comcast.net> (raw)
In-Reply-To: <CADPb22Q6HDzra-EPPXCUHOn-T1snsc14-oOH13crZZqfdUi7Gg@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=windows-1252, Size: 3737 bytes --]

On Jun 17, 2015, at 2:26 PM, Doug Evans <dje@google.com> wrote:
> Can you try using one of the newer methods?
> [it's the with_ql version that uses CRAZY_MAX_THREADS]

Ah, I was mistaken:

remote_ops.to_find_new_threads = remote_threads_info;  

and yet:

static void
remote_find_new_threads (void)
{
  remote_threadlist_iterator (remote_newthread_step, 0,
                              CRAZY_MAX_THREADS);
}

I was assuming that I was going to go in through the top using this routine.  As you say, remote_threads_info doesn’t have the limitation, and since I  already use qfThreadInfo, I should be good.  I see that trunk already fixed up the names nicely.

Thanks.
From gdb-return-44441-listarch-gdb=sources.redhat.com@sourceware.org Fri Jun 19 09:37:28 2015
Return-Path: <gdb-return-44441-listarch-gdb=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb@sources.redhat.com
Received: (qmail 19276 invoked by alias); 19 Jun 2015 09:37:27 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Delivered-To: mailing list gdb@sourceware.org
Received: (qmail 19261 invoked by uid 89); 19 Jun 2015 09:37:26 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-pd0-f180.google.com
Received: from mail-pd0-f180.google.com (HELO mail-pd0-f180.google.com) (209.85.192.180) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 19 Jun 2015 09:37:24 +0000
Received: by pdjm12 with SMTP id m12so87121895pdj.3        for <gdb@sourceware.org>; Fri, 19 Jun 2015 02:37:22 -0700 (PDT)
X-Received: by 10.66.222.130 with SMTP id qm2mr29995980pac.39.1434706642523;        Fri, 19 Jun 2015 02:37:22 -0700 (PDT)
Received: from E107787-LIN (gcc1-power7.osuosl.org. [140.211.15.137])        by mx.google.com with ESMTPSA id cf1sm10626810pdb.41.2015.06.19.02.37.20        (version=TLSv1.2 cipher=RC4-SHA bits\x128/128);        Fri, 19 Jun 2015 02:37:21 -0700 (PDT)
From: Yao Qi <qiyaoltc@gmail.com>
To: Sergio Durigan Junior <sergiodj@sergiodj.net>
Cc: GDB <gdb@sourceware.org>
Subject: Re: [BuildBot] News and announcements
References: <87616mmcks.fsf@sergiodj.net>
Date: Fri, 19 Jun 2015 09:37:00 -0000
In-Reply-To: <87616mmcks.fsf@sergiodj.net> (Sergio Durigan Junior's message of	"Wed, 17 Jun 2015 14:09:23 -0400")
Message-ID: <86fv5orqd0.fsf@gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
X-SW-Source: 2015-06/txt/msg00046.txt.bz2
Content-length: 664

Sergio Durigan Junior <sergiodj@sergiodj.net> writes:

> Needless to say, we also welcome donations of new machines for our
> BuildBot!  For example, we don't have an ARM buildslave yet, which would
> be very nice.  So if you're interested in helping us, you can either
> take a look at this wiki page:
>
>   <https://sourceware.org/gdb/wiki/BuildBot>

Hi Sergio,
Does buildmaster need to access to buildslave?  Is it OK that the
buildslave is put behind the firewall?  I'd like to know how these
arm or aarch64 buildslaves are used in BuildBot, and see how to provide
them from linaro or arm (and whether it is allowed to do so).

-- 
Yao (齐尧)


      reply	other threads:[~2015-06-18  1:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 17:27 Crazy? Mike Stump
2015-06-17 21:27 ` Crazy? Doug Evans
2015-06-18  1:21   ` Mike Stump [this message]

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=9F4CA95A-E896-4B86-9037-C3C14D21FEC5@comcast.net \
    --to=mikestump@comcast.net \
    --cc=dje@google.com \
    --cc=gdb@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