From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: remove uses of iterate_over_inferiors in remote-sim.c
Date: Wed, 22 Jan 2020 01:56:00 -0000 [thread overview]
Message-ID: <56330e60-ca70-5ba8-e751-1db8229ed6e8@simark.ca> (raw)
In-Reply-To: <87muag2uah.fsf@tromey.com>
On 2020-01-21 7:45 p.m., Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
>
> Simon> The only remaining use is in darwin-nat.c, but we need to un-break it
> Simon> first (it doesn't build following multi-target).
>
> I will try to look at this soon.
I have it building here:
https://github.com/simark/binutils-gdb/tree/darwin-nat-multi-target
But I haven't tested it. I plan on finishing it and sending a patch eventually,
but if you want to do it before me, I won't object.
Simon
prev parent reply other threads:[~2020-01-22 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 2:14 Simon Marchi
2020-01-21 20:17 ` Tom Tromey
2020-01-21 21:09 ` Simon Marchi
2020-01-21 21:29 ` Tom Tromey
2020-01-21 22:28 ` Simon Marchi
2020-01-22 1:31 ` Tom Tromey
2020-01-22 1:56 ` Simon Marchi [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=56330e60-ca70-5ba8-e751-1db8229ed6e8@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
--cc=tom@tromey.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