From: <Paul_Koning@Dell.com>
To: <gbenson@redhat.com>
Cc: <sandra@codesourcery.com>, <gdb@sourceware.org>
Subject: Re: GDB now takes 4 minutes to start up with remote gdbserver target
Date: Fri, 24 Jul 2015 15:27:00 -0000 [thread overview]
Message-ID: <FC7D3C21-A8E8-4316-8125-E9FCE152F5D0@dell.com> (raw)
In-Reply-To: <20150724151148.GA18553@blade.nx>
> 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
next prev parent reply other threads:[~2015-07-24 15:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 23:21 Sandra Loosemore
2015-07-24 2:39 ` Sandra Loosemore
2015-07-24 8:52 ` Gary Benson
2015-07-24 13:59 ` Sandra Loosemore
2015-07-24 14:08 ` Paul_Koning
2015-07-24 15:11 ` Gary Benson
2015-07-24 15:27 ` Paul_Koning [this message]
2015-07-24 16:36 ` Pedro Alves
2015-07-24 16:58 ` Paul_Koning
2015-07-28 22:12 ` Pedro Alves
2015-07-24 17:19 ` Sandra Loosemore
2015-07-27 12:22 ` Gary Benson
2015-07-28 9:25 ` Gary Benson
2015-07-28 15:22 ` Sandra Loosemore
2015-07-29 10:00 ` Gary Benson
2015-07-28 15:38 ` Gary Benson
2015-07-28 17:04 ` Doug Evans
2015-07-28 22:13 ` Pedro Alves
2015-07-29 1:32 ` Sandra Loosemore
2015-07-26 20:03 ` Frank Ch. Eigler
2015-07-26 20:06 ` Jan Kratochvil
2015-07-26 20:50 ` Frank Ch. Eigler
2015-07-28 16:55 ` Doug Evans
2015-07-28 22:14 ` Pedro Alves
2015-07-29 10:39 ` Gary Benson
2015-07-29 16:54 ` Jan Kratochvil
2015-07-29 10:15 ` Gary Benson
2015-07-24 10:34 ` Gary Benson
2015-07-24 16:05 ` Sandra Loosemore
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=FC7D3C21-A8E8-4316-8125-E9FCE152F5D0@dell.com \
--to=paul_koning@dell.com \
--cc=gbenson@redhat.com \
--cc=gdb@sourceware.org \
--cc=sandra@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).