On Wed, 12 Feb 2020, Pedro Alves wrote:
> > That's actually quite similar to what I considered first, before I
> > changed my mind. Whatever.
>
> Doing it in gdbserver/ has the advantage that it stays under gdbserver's
> control, so it doesn't need syncing code with the gcc tree. I know of at
> least one off-tree port that uses gdbserver in a host != target scenario,
> so I imagine that this condition will evolve over time.
Sure, that makes sense to me.
> > case "${host}" in
> > + ${target})
> > + gdbserver_host=${host}
> > + ;;
> > + *)
> > + gdbserver_host=NONE
> > + ;;
> if/else reads more to-the-point to me, so I tweaked it that
> way, and merged it in (to binutils-gdb), like below.
Great, thanks for handling this!
> I'm sorry for not noticing your earlier patch.
No worries, I'm glad we've got this sorted.
Maciej
