public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Move gdb_notifier comment Date: Mon, 13 Apr 2020 21:10:43 +0000 (GMT) [thread overview] Message-ID: <20200413211043.2710B39518AC@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7990abcc9b7d96f16ea51076685d4dfa7d503fe3 commit 7990abcc9b7d96f16ea51076685d4dfa7d503fe3 Author: Tom Tromey <tom@tromey.com> Date: Mon Apr 13 12:42:59 2020 -0600 Move gdb_notifier comment This moves the gdb_notifier comment a bit lower in event-loop.c, to where it belongs; and removes an obsolete comment that Pedro pointed out. gdbsupport/ChangeLog 2020-04-13 Tom Tromey <tom@tromey.com> * event-loop.c: Move comment. Remove obsolete comment. Diff: --- gdbsupport/ChangeLog | 4 ++++ gdbsupport/event-loop.cc | 19 ++++++++----------- 2 files changed, 12 insertions(+), 11 deletions(-) diff --git a/gdbsupport/ChangeLog b/gdbsupport/ChangeLog index 1e64022c7c9..cd7033d58d6 100644 --- a/gdbsupport/ChangeLog +++ b/gdbsupport/ChangeLog @@ -1,3 +1,7 @@ +2020-04-13 Tom Tromey <tom@tromey.com> + + * event-loop.c: Move comment. Remove obsolete comment. + 2020-04-13 Tom Tromey <tom@tromey.com> * event-loop.h: Move from ../gdb/. diff --git a/gdbsupport/event-loop.cc b/gdbsupport/event-loop.cc index f7ccc4eec47..e959e1b91b8 100644 --- a/gdbsupport/event-loop.cc +++ b/gdbsupport/event-loop.cc @@ -57,17 +57,6 @@ typedef struct file_handler } file_handler; -/* Gdb_notifier is just a list of file descriptors gdb is interested in. - These are the input file descriptor, and the target file - descriptor. We have two flavors of the notifier, one for platforms - that have the POLL function, the other for those that don't, and - only support SELECT. Each of the elements in the gdb_notifier list is - basically a description of what kind of events gdb is interested - in, for each fd. */ - -/* As of 1999-04-30 only the input file descriptor is registered with the - event loop. */ - /* Do we use poll or select ? */ #ifdef HAVE_POLL #define USE_POLL 1 @@ -82,6 +71,14 @@ static unsigned char use_poll = USE_POLL; #include <io.h> #endif +/* Gdb_notifier is just a list of file descriptors gdb is interested in. + These are the input file descriptor, and the target file + descriptor. We have two flavors of the notifier, one for platforms + that have the POLL function, the other for those that don't, and + only support SELECT. Each of the elements in the gdb_notifier list is + basically a description of what kind of events gdb is interested + in, for each fd. */ + static struct { /* Ptr to head of file handler list. */
reply other threads:[~2020-04-13 21:10 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200413211043.2710B39518AC@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).