From: Gary Benson <gbenson@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Sandra Loosemore <sandra@codesourcery.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:38:00 -0000 [thread overview]
Message-ID: <20150728153838.GA31325@blade.nx> (raw)
In-Reply-To: <20150728092507.GA28545@blade.nx>
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:"
>
> There's a new boolean here, "set auto-target-prefix on|off", which
> is enabled by default.
>
> So:
>
> gdb; target remote :9999 -> "target:" prefix applied
> gdb FILE; target remote :9999 -> no "target:" prefix
>
> The latter is how Sandra is invoking GDB. Also:
>
> gdb -n PID, and
> gdb; attach PID -> "target:" prefix applied iff FS is nonlocal
>
> Aside from the fact that this should fix Sandra's use case without
> breaking any I care about, I like that users doing non-remote, non-
> container debugging will not see "target:" prefixes onscreen unless
> they're actually necessary.
I've submitted a series of the work I've done on this:
https://sourceware.org/ml/gdb-patches/2015-07/msg00828.html
Please reply to that thread instead of this.
Thanks,
Gary
--
http://gbenson.net/
next prev parent reply other threads:[~2015-07-28 15:38 UTC|newest]
Thread overview: 25+ 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-26 20:03 ` Frank Ch. Eigler
2015-07-26 20:06 ` Jan Kratochvil
2015-07-26 20:50 ` Frank Ch. Eigler
[not found] ` <55B27348.1020104@codesourcery.com>
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 [this message]
2015-07-28 17:04 ` Doug Evans
2015-07-28 22:13 ` Pedro Alves
2015-07-29 1:32 ` Sandra Loosemore
2015-07-28 16:55 ` Doug Evans
2015-07-28 22:14 ` Pedro Alves
2015-07-29 10:39 ` Gary Benson
2015-07-29 10:15 ` Gary Benson
2015-07-24 10:34 ` Gary Benson
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=20150728153838.GA31325@blade.nx \
--to=gbenson@redhat.com \
--cc=Paul_Koning@Dell.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--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