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] Make stdin_event_handler static Date: Tue, 20 Sep 2022 20:05:04 +0000 (GMT) [thread overview] Message-ID: <20220920200504.309F83858C74@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=63b3ec661a06acb4fa722c618a6b0003e5e141c3 commit 63b3ec661a06acb4fa722c618a6b0003e5e141c3 Author: Tom Tromey <tom@tromey.com> Date: Fri Aug 26 16:48:24 2022 -0600 Make stdin_event_handler static I noticed that stdin_event_handler is only used in event-top.c, so this patch changes it to be 'static'. Diff: --- gdb/event-top.c | 2 +- gdb/event-top.h | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/gdb/event-top.c b/gdb/event-top.c index 00adbe8fb4f..88c53b720a9 100644 --- a/gdb/event-top.c +++ b/gdb/event-top.c @@ -497,7 +497,7 @@ get_command_line_buffer (void) instead of calling gdb_readline_no_editing_callback, give gdb a chance to detect errors and do something. */ -void +static void stdin_event_handler (int error, gdb_client_data client_data) { struct ui *ui = (struct ui *) client_data; diff --git a/gdb/event-top.h b/gdb/event-top.h index 722e636a110..883ad191115 100644 --- a/gdb/event-top.h +++ b/gdb/event-top.h @@ -45,7 +45,6 @@ extern void handle_sigtstp (int sig); extern void handle_sigint (int sig); extern void handle_sigterm (int sig); extern void async_request_quit (void *arg); -extern void stdin_event_handler (int error, void *client_data); extern void async_disable_stdin (void); extern void async_enable_stdin (void);
reply other threads:[~2022-09-20 20:05 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=20220920200504.309F83858C74@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).