From: Jiong Wang <jiong.wang@arm.com>
To: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/4] Merge remote thread listing methods
Date: Fri, 17 Oct 2014 08:57:00 -0000 [thread overview]
Message-ID: <5440D9FB.8000509@arm.com> (raw)
In-Reply-To: <1412266896-28210-2-git-send-email-palves@redhat.com>
On 02/10/14 17:21, Pedro Alves wrote:
> +
> +static void
> +remote_threads_info (struct target_ops *ops)
> +{
> + struct remote_state *rs = get_remote_state ();
> + struct threads_listing_context context;
> + struct cleanup *old_chain;
> +
> + context.items = NULL;
> + old_chain = make_cleanup (clear_threads_listing_context, &context);
>
Hi Pedro,
looks like this change break arm native build on chrome book.
clear_threads_listing_context only exist when HAVE_LIBEXPACT defined.
Reagrds,
Jiong
next prev parent reply other threads:[~2014-10-17 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 16:21 [PATCH 0/4] remote thread listing: get rid of unnecessary "thread alive?" traffic Pedro Alves
2014-10-02 16:21 ` [PATCH 4/4] DEC threads: Simplify updating the thread list Pedro Alves
2014-10-02 18:46 ` Mark Kettenis
2014-10-03 9:12 ` Pedro Alves
2014-10-02 16:21 ` [PATCH 2/4] Push pruning old threads down to the target Pedro Alves
2016-12-09 6:38 ` Thomas Schwinge
2014-10-02 16:21 ` [PATCH 3/4] remote: get rid of all the T packets when synching the thread list Pedro Alves
2014-10-02 16:21 ` [PATCH 1/4] Merge remote thread listing methods Pedro Alves
2014-10-17 8:57 ` Jiong Wang [this message]
2014-10-17 10:17 ` [PATCH] Fix build without libexpat (Re: [PATCH 1/4] Merge remote thread listing methods) Pedro Alves
2014-10-17 10:21 ` Jiong Wang
2014-10-15 22:01 ` [pushed] Re: [PATCH 0/4] remote thread listing: get rid of unnecessary "thread alive?" traffic Pedro Alves
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=5440D9FB.8000509@arm.com \
--to=jiong.wang@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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