From: fche@redhat.com (Frank Ch. Eigler)
To: Pedro Alves <palves@redhat.com>
Cc: Stan Cox <scox@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFC][PATCH v2] Consolidate gdbserver global variables
Date: Mon, 07 May 2018 19:17:00 -0000 [thread overview]
Message-ID: <87in7zjmxk.fsf@redhat.com> (raw)
In-Reply-To: <9988957e-3bf8-cbe8-6c08-58706b11bd60@redhat.com> (Pedro Alves's message of "Fri, 4 May 2018 15:13:53 +0100")
palves wrote:
> [...]
> Some comments more. I still have some design reservations.
> It seems to me that simply making some of the globals be
> per client along won't work correctly. Particularly, the
> cases where the globals are used in the backends.
> [...]
I don't want to speak for Stan here, but I suspect all this is about is
the breaking up of the multi-client work along the patchset path your
requested. Yup, indeed backends have to do the logical 'union' of the
work that all the clients request, and each client interface will have
to filter the notifications correspondingly to undo the 'union'.
But all that is in a separate patch; this part seems to simply
reorganize the globals in preparation for that, as you asked.
- FChE
next prev parent reply other threads:[~2018-05-07 19:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 22:03 [RFC][PATCH] " Stan Cox
2018-01-31 3:41 ` Stan Cox
2018-04-23 17:58 ` Pedro Alves
2018-05-03 15:06 ` [RFC][PATCH v2] " Stan Cox
2018-05-04 14:14 ` Pedro Alves
2018-05-07 19:17 ` Frank Ch. Eigler [this message]
2018-05-25 14:31 ` Pedro Alves
2018-05-08 20:58 ` [RFC][PATCH v3] " Stan Cox
2018-05-25 15:01 ` Pedro Alves
2018-05-29 20:46 ` Stan Cox
2018-05-30 14:30 ` Pedro Alves
2018-06-08 16:11 ` Tom Tromey
2018-06-08 16:46 ` Stan Cox
2018-06-08 16:52 ` Tom Tromey
2018-07-10 1:14 ` Sergio Durigan Junior
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=87in7zjmxk.fsf@redhat.com \
--to=fche@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=scox@redhat.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).