From: Tom Tromey <tromey@redhat.com>
To: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Cc: James Greenhalgh <james.greenhalgh@arm.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC 0/2] let gdbserver use libiberty
Date: Thu, 19 Jun 2014 14:48:00 -0000 [thread overview]
Message-ID: <87vbrxc5vm.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAFqB+Pyp_=QavC0HYOpmZBvHuiCNu8Z_geCaa3-Rm5xC1Or1Lw@mail.gmail.com> (Marcus Shawcroft's message of "Wed, 18 Jun 2014 13:27:39 +0100")
>>>>> "Marcus" == Marcus Shawcroft <marcus.shawcroft@gmail.com> writes:
Marcus> An alternative approach to that suggested by James is to have the
Marcus> gdbserver configure scri[t probe for AR to ensure that something sane
Marcus> is passed on to the sub-builds.
Marcus> Patch attached.
Marcus> OK ?
Yes, this is ok. Thanks.
Tom
next prev parent reply other threads:[~2014-06-19 14:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 18:49 Tom Tromey
2014-01-20 18:49 ` [RFC 2/2] delete gdbserver's freeargv Tom Tromey
2014-02-07 16:35 ` Pedro Alves
2014-01-20 18:49 ` [RFC 1/2] link gdbserver against libiberty Tom Tromey
2014-01-21 1:49 ` Yao Qi
2014-01-21 2:33 ` Tom Tromey
2014-02-07 14:49 ` Tom Tromey
2014-02-07 16:32 ` Pedro Alves
2014-02-07 21:00 ` Tom Tromey
2014-02-10 13:27 ` Pedro Alves
2014-02-12 16:44 ` Tom Tromey
2014-02-12 16:49 ` Pedro Alves
2014-02-08 2:36 ` Yao Qi
2014-01-21 2:03 ` Yao Qi
2014-01-20 18:54 ` [RFC 0/2] let gdbserver use libiberty Tom Tromey
2014-06-12 20:37 ` Tom Tromey
2014-06-16 13:26 ` James Greenhalgh
2014-06-18 12:27 ` Marcus Shawcroft
2014-06-19 14:48 ` Tom Tromey [this message]
2014-06-20 10:52 ` Pedro Alves
2014-06-20 12:01 ` Gary Benson
2014-06-20 14:16 ` Tom Tromey
2014-06-20 14:44 ` [COMMITTED PATCH] Fix mingw32 build on x86-64 RHEL 6.5 Gary Benson
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=87vbrxc5vm.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=james.greenhalgh@arm.com \
--cc=marcus.shawcroft@gmail.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