public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: Gary Benson <gbenson@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, <Paul_Koning@Dell.com>,
	<gdb@sourceware.org>
Subject: Re: GDB now takes 4 minutes to start up with remote gdbserver target
Date: Tue, 28 Jul 2015 15:22:00 -0000	[thread overview]
Message-ID: <55B79DD6.1000200@codesourcery.com> (raw)
In-Reply-To: <20150728092507.GA28545@blade.nx>

On 07/28/2015 03:25 AM, Gary Benson wrote:
>
> Ok, here goes...
>
>   * From a user's perspective GDB is magically prefixing *some*
>     executable and shared library filenames with "target:".
>
>   * From a developer's perspective this magic prefixing is implemented
>     by having the string "target:" as the default sysroot.
>
> My proposal is to make the default sysroot be "" again, and add the
> prefix in solib_find_1 if certain conditions are met, specifically:
>
>   * Executable filenames get prefixed with "target:" iff:
>       Automatic "target:" prefixing is enabled
>       AND gdb_sysroot is ""
>       AND the filesystem is nonlocal
>
>   * Shared library filenames get prefixed with "target:" iff:
>       Automatic "target:" prefixing is enabled
>       AND gdb_sysroot is ""
>       AND the filesystem is nonlocal
>       AND exec_filename starts with "target:"

Can you explain what "the filesystem is nonlocal" means?  Which 
filesystem?  Nonlocal relative to the host or the target?  And what 
qualifies as nonlocal -- e.g. are NFS or SSHFS mounts nonlocal?

-Sandra the confused

  reply	other threads:[~2015-07-28 15:22 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
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 [this message]
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=55B79DD6.1000200@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=Paul_Koning@Dell.com \
    --cc=gbenson@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=palves@redhat.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).