From: Pedro Alves <palves@redhat.com>
To: Gary Benson <gbenson@redhat.com>, gdb-patches@sourceware.org
Cc: "Sandra Loosemore" <sandra@codesourcery.com>,
"Doug Evans" <dje@google.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: Fri, 21 Aug 2015 15:16:00 -0000 [thread overview]
Message-ID: <55D740D6.9030108@redhat.com> (raw)
In-Reply-To: <1438788496-32246-3-git-send-email-gbenson@redhat.com>
On 08/05/2015 04:28 PM, 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.
OK.
Hopefully BFD doesn't get corrupted when an exception crosses it.
If it does, then we'll need to catch all exceptions before returning
to BFD, and return some "silently abort whatever you're doing" error.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-08-21 15:16 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
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 ` Pedro Alves [this message]
2015-08-21 16:23 ` [pushed] Make remote file " 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=55D740D6.9030108@redhat.com \
--to=palves@redhat.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=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