From: xdje42@gmail.com
To: gdb-patches@sourceware.org
Subject: [PATCH v1 13/13] script language API for GDB: utils.c changes
Date: Fri, 06 Dec 2013 05:53:00 -0000 [thread overview]
Message-ID: <52a16654.669c420a.3650.ffffc993@mx.google.com> (raw)
This patch contains the changes to utils.c.
The clear/set/check_quit_flag functions now live in scripting.c.
2013-12-05 Doug Evans <xdje42@gmail.com>
* utils.c (quit_flag): Delete, moved to scripting.c.
(clear_quit_flag, set_quit_flag, check_quit_flag): Delete, moved to
scripting.c.
diff --git a/gdb/utils.c b/gdb/utils.c
index 975c432..e1de41a 100644
--- a/gdb/utils.c
+++ b/gdb/utils.c
@@ -112,12 +112,6 @@ static int debug_timestamp = 0;
int job_control;
-#ifndef HAVE_PYTHON
-/* Nonzero means a quit has been requested. */
-
-int quit_flag;
-#endif /* HAVE_PYTHON */
-
/* Nonzero means quit immediately if Control-C is typed now, rather
than waiting until QUIT is executed. Be careful in setting this;
code which executes with immediate_quit set has to be very careful
@@ -131,41 +125,6 @@ int quit_flag;
int immediate_quit;
-#ifndef HAVE_PYTHON
-
-/* Clear the quit flag. */
-
-void
-clear_quit_flag (void)
-{
- quit_flag = 0;
-}
-
-/* Set the quit flag. */
-
-void
-set_quit_flag (void)
-{
- quit_flag = 1;
-}
-
-/* Return true if the quit flag has been set, false otherwise. */
-
-int
-check_quit_flag (void)
-{
- /* This is written in a particular way to avoid races. */
- if (quit_flag)
- {
- quit_flag = 0;
- return 1;
- }
-
- return 0;
-}
-
-#endif /* HAVE_PYTHON */
-
/* Nonzero means that strings with character values >0x7F should be printed
as octal escapes. Zero means just print the value (e.g. it's an
international character, and the terminal or window can cope.) */
reply other threads:[~2013-12-06 5:53 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=52a16654.669c420a.3650.ffffc993@mx.google.com \
--to=xdje42@gmail.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).