GDB now takes 4 minutes to start up with remote gdbserver target

[Paul_Koning@Dell.com]

> On Jul 24, 2015, at 11:11 AM, Gary Benson <gbenson@redhat.com> wrote:
> 
> Paul_Koning@dell.com wrote:
>> Sandra Loosemore wrote:
>>> I'd rather that we fix GDB to "just work", as it used to do,
>>> rather than have to document workarounds for this breakage.
>> 
>> I agree.  Taking multiple minutes to start up, by defaut, is a bug.
> 
> I also agree that GDB suddenly taking very much longer to start up
> is a bug.  I don't need convincing, we're all on the same page here.
> 
> I don't agree that the fix is reverting the "target:" sysroot
> changes.  While that would make GDB "just work" for Sandra's
> scenario, it would make GDB not "just work" for other scenarios.

But having sysroot default to target is also a bad idea for lots of other people.  Consider embedded systems: you presumably have stripped images there, but unstripped ones on your build host.  Flipping the default sysroot to target means that suddenly you don’t see debug symbols any more.  I don’t see how that can be a good thing.

Also, remote file access is always slower.  Especially when using a protocol such as the GDB remote protocol that is a single operation request/response protocol designed only for simplicity, not at all for performance.

	paul