From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Invalid file I/O file handles when the target closes
Date: Tue, 10 Apr 2018 10:11:00 -0000 [thread overview]
Message-ID: <20180410101145.18136-1-palves@redhat.com> (raw)
Found this little easily-splittable piece on my multi-target branch,
thought I'd send it out.
On the branch, we can connect to multiple remote servers
simultaneously. Each remote connection is managed by a separate
heap-allocated target_ops instance. The change from a single global
remote target_ops heap-allocated target_ops instances exposed the
problem fixed in patch #2.
Pedro Alves (2):
C++ify fileio_fh_t, replace VEC with std::vector
File I/O file handles after target closes
gdb/remote.c | 3 +-
gdb/target.c | 108 ++++++++++++++++++++++++++++++++++++++---------------------
2 files changed, 70 insertions(+), 41 deletions(-)
--
2.14.3
next reply other threads:[~2018-04-10 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 10:11 Pedro Alves [this message]
2018-04-10 10:11 ` [PATCH 1/2] C++ify fileio_fh_t, replace VEC with std::vector Pedro Alves
2018-04-10 10:11 ` [PATCH 2/2] File I/O file handles after target closes Pedro Alves
2018-04-11 3:33 ` [PATCH 0/2] Invalid file I/O file handles when the " Simon Marchi
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=20180410101145.18136-1-palves@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
/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).