From: Gary Benson <gbenson@redhat.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: gdb-patches@sourceware.org, "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 2/2] Make remote file transfers interruptible
Date: Tue, 11 Aug 2015 10:52:00 -0000 [thread overview]
Message-ID: <20150811105221.GA22087@blade.nx> (raw)
In-Reply-To: <55C3A10F.3010106@codesourcery.com>
Hi Sandra,
Sandra Loosemore wrote:
> On 08/05/2015 09:28 AM, Gary Benson wrote:
> > This commit makes it possible to interrupt slow remote file transfers.
> >
> > gdb/ChangeLog:
> >
> > * gdb_bfd.c (gdb_bfd_iovec_fileio_pread): Add QUIT call.
>
> I think that this is the same patch that you sent earlier:
>
> https://sourceware.org/ml/gdb/2015-07/msg00043.html
>
> It still does not work for me. :-(
Ok, given the packet-size limit of RSP I was assuming GDB would read
the files in chunks the size of the server's packet buffer size (16k
for gdbserver) but it seems that that chunking happens at a lower
level, so the interrupt is only noticed between files rather than
between chunks. I tested this patch using "remote get", but it seems
that that operates differently. So I'm retracting this patch.
Making remote transfers properly interruptible looks like a fairly
involved task that's only slightly on my radar. I've filed a bug
(https://sourceware.org/bugzilla/show_bug.cgi?id=18804) to keep the
issue from being forgotten. I'll work on if I have some free time,
or someone else can do it.
The other patch in the series (the warning messages) can go in if
people find it useful.
Thanks,
Gary
--
http://gbenson.net/
next prev parent reply other threads:[~2015-08-11 10:52 UTC|newest]
Thread overview: 20+ 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 1/2] Warn when accessing binaries over RSP Gary Benson
2015-08-11 11:55 ` Andrew Burgess
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-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 [this message]
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
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=20150811105221.GA22087@blade.nx \
--to=gbenson@redhat.com \
--cc=Paul_Koning@Dell.com \
--cc=apoenitz@t-online.de \
--cc=dje@google.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