From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Gary Benson <gbenson@redhat.com>
Cc: gdb-patches@sourceware.org,
"Sandra Loosemore" <sandra@codesourcery.com>,
"Doug Evans" <dje@google.com>, "Pedro Alves" <palves@redhat.com>,
"Jan Kratochvil" <jan.kratochvil@redhat.com>,
"André Pönitz" <apoenitz@t-online.de>,
Paul_Koning@Dell.com
Subject: Re: [PATCH 1/2] Warn when accessing binaries over RSP
Date: Tue, 11 Aug 2015 11:55:00 -0000 [thread overview]
Message-ID: <20150811115538.GA7352@embecosm.com> (raw)
In-Reply-To: <1438788496-32246-2-git-send-email-gbenson@redhat.com>
* Gary Benson <gbenson@redhat.com> [2015-08-05 16:28:15 +0100]:
>
> diff --git a/gdb/gdb_bfd.c b/gdb/gdb_bfd.c
> index 1781d80..b511777 100644
> --- a/gdb/gdb_bfd.c
> +++ b/gdb/gdb_bfd.c
> @@ -219,13 +219,38 @@ gdb_bfd_iovec_fileio_open (struct bfd *abfd, void *inferior)
> const char *filename = bfd_get_filename (abfd);
> int fd, target_errno;
> int *stream;
> + struct target_ops *ops = find_target_at (process_stratum);
>
> gdb_assert (is_target_filename (filename));
> + filename += strlen (TARGET_SYSROOT_PREFIX);
> +
> + /* GDB provides no indicator of progress during file operations, and
> + can appear to have locked up during slow remote transfers, so we
> + inform the user what is happening and suggest a way out. It's
> + unpleasant that we need to detect remote targets this way (rather
> + than putting the warnings in remote_hostio_open), but it's not
> + possible for remote_hostio_open to differentiate between
> + accessing inferior binaries (which can be bypassed) and accessing
> + things like /proc/ (which is unavoidable). */
> + if (strcmp (ops->to_shortname, "remote") == 0
> + || strcmp (ops->to_shortname, "extended-remote") == 0)
> + {
> + static int warning_issued = 0;
> +
> + printf_unfiltered (_("Reading %s from remote target\n"),
> + filename);
> +
> + if (!warning_issued)
> + {
> + warning (_("File transfers from remote targets can be slow.\n"
> + "Use \"set sysroot\" to access files locally"
> + " instead."));
> + warning_issued = 1;
> + }
> + }
Altering the behaviour based on to_shortname feels like breaking this
nice target OO model we have.
Could the warning not be moved down into target_fileio_open instead?
Or if that's really not an appropriate place should we add a new
target method?
Thanks,
Andrew
next prev parent reply other threads:[~2015-08-11 11:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 15:28 [PATCH 0/2] Better handling of slow remote transfers Gary Benson
2015-08-05 15:28 ` [PATCH 2/2] Make remote file transfers interruptible Gary Benson
2015-08-06 18:03 ` Sandra Loosemore
2015-08-11 10:52 ` Gary Benson
2015-08-12 14:30 ` [PATCH] Make remote " Gary Benson
2015-08-12 17:33 ` Sandra Loosemore
2015-08-12 17:40 ` Doug Evans
2015-08-13 9:10 ` Gary Benson
2015-08-14 18:37 ` Joel Brobecker
2015-08-17 16:00 ` Pedro Alves
2015-08-17 18:54 ` Sandra Loosemore
2015-08-21 15:16 ` [PATCH 2/2] Make remote file " Pedro Alves
2015-08-21 16:23 ` [pushed] " Gary Benson
2015-08-05 15:28 ` [PATCH 1/2] Warn when accessing binaries over RSP Gary Benson
2015-08-11 11:55 ` Andrew Burgess [this message]
2015-08-11 14:04 ` Gary Benson
2015-08-13 13:24 ` [PATCH v2] Warn when accessing binaries from remote targets Gary Benson
2015-08-13 15:07 ` Andrew Burgess
2015-08-21 15:41 ` Pedro Alves
2015-08-21 16:23 ` [pushed] " Gary Benson
2015-08-11 17:15 [PATCH 1/2] Warn when accessing binaries over RSP Doug Evans
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=20150811115538.GA7352@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=Paul_Koning@Dell.com \
--cc=apoenitz@t-online.de \
--cc=dje@google.com \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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