From: "Pedro Alves (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Tom Tromey <tromey@sourceware.org>, gdb-patches@sourceware.org
Subject: [review v3] Introduce run_on_main_thread
Date: Fri, 22 Nov 2019 18:39:00 -0000 [thread overview]
Message-ID: <20191122183851.D009B2816F@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1571543710000.I16ef82f0564e9f8a524bdc64cb31df79a988ad9f@gnutoolchain-gerrit.osci.io>
Pedro Alves has posted comments on this change.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/170
......................................................................
Patch Set 3: Code-Review+2
(2 comments)
| --- gdb/ser-event.c
| +++ gdb/ser-event.c
| @@ -220,0 +228,19 @@ /* The serial event used when posting runnables. */
| +
| +static struct serial_event *runnable_event;
| +
| +/* Runnables that have been posted. */
| +
| +static std::vector<std::function<void ()>> runnables;
| +
| +#if CXX_STD_THREAD
| +
| +/* Mutex to hold when handling runnable_event or runnables. */
PS3, Line 237:
Uppercase runnable_event / runnables ?
| +
| +static std::mutex runnable_mutex;
| +
| +#endif
| +
| +/* Run all the queued runnables. */
| +
| +static void
| +run_events (int error, gdb_client_data client_data)
| --- /dev/null
| +++ gdb/unittests/main-thread-selftests.c
| @@ -1,0 +68,13 @@ run_tests ()
| +#endif
| +
| +}
| +}
| +
| +void
| +_initialize_main_thread_selftests ()
| +{
| +#if CXX_STD_THREAD
| + selftests::register_test ("main_thread",
PS3, Line 77:
Any reason this isn't named "run_on_main_thread"?
Just thinking about whether that would make "maint info selftests"
output more obvious. I imagine that that command could have a
completer and "maint info selftests run_on<TAB>" would be the obvious
thing to typo.
Actually, this is so minor that I don't know why I'm mentioning it.
Please ignore. :-D
Thanks much for adding the unit test.
| + selftests::main_thread_tests::run_tests);
| +#endif
| +}
--
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: I16ef82f0564e9f8a524bdc64cb31df79a988ad9f
Gerrit-Change-Number: 170
Gerrit-PatchSet: 3
Gerrit-Owner: Tom Tromey <tromey@sourceware.org>
Gerrit-Reviewer: Pedro Alves <palves@redhat.com>
Gerrit-Comment-Date: Fri, 22 Nov 2019 18:38:49 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
next prev parent reply other threads:[~2019-11-22 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 4:02 [review] " Tom Tromey (Code Review)
2019-10-30 22:54 ` [review v3] " Tom Tromey (Code Review)
2019-11-22 18:39 ` Pedro Alves (Code Review) [this message]
2019-11-22 19:00 ` Pedro Alves (Code Review)
2019-11-22 23:05 ` Tom Tromey (Code Review)
2019-11-22 23:50 ` [review v4] " Tom Tromey (Code Review)
2019-11-26 15:46 ` Pedro Alves (Code Review)
2019-11-26 21:13 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-26 21:14 ` Sourceware to Gerrit sync (Code Review)
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=20191122183851.D009B2816F@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=gdb-patches@sourceware.org \
--cc=gnutoolchain-gerrit@osci.io \
--cc=tromey@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