public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Gary Benson <gbenson@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, Doug Evans <dje@google.com>,
	       Sandra Loosemore <sandra@codesourcery.com>,
	       "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GDB now takes 4 minutes to start up with remote gdbserver target
Date: Wed, 29 Jul 2015 16:54:00 -0000	[thread overview]
Message-ID: <20150729165438.GA6083@host1.jankratochvil.net> (raw)
In-Reply-To: <20150729103948.GD19548@blade.nx>

On Wed, 29 Jul 2015 12:39:48 +0200, Gary Benson wrote:
> Yes.  Jan told me he was considering changing sysroot to a multiple-
> component path, with the default being something like "/:target:/".
> This should work really nicely, but it only makes sense with build-id
> validation (it's just too easy to get the wrong files otherwise).

> I'm assuming we can cope with the fact that the separator ":" appears
> in "target:" somehow :)

Yes, if a parsed component is "target" it is merged back with the next one.
	https://sourceware.org/git/?p=archer.git;a=commitdiff;h=972af46ddba59d32ba903da5bd736bc6239a1958#patch2


> > If resolving the interruptability and adding a suggestive warning
> > is deemed insufficient resolution (though I think we should try it
> > first), then I think it's too late to add too much magic, and we should
> > change the default sysroot back to "" by default.  Users can still then
> > put "set sysroot target:" in .gdbinit with 7.10, and we can continue
> > addressing identified issues until "target:" (or something around it)
> > can be made the default, on master.
> 
> I'm going to look at adding a warning.

There should be also some 'set' possibility to suppress that warning if one
knows what s/he is doing.


Jan

  reply	other threads:[~2015-07-29 16:54 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
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 [this message]
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=20150729165438.GA6083@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=gbenson@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).