+2004-07-16 Andrew Cagney <cagney@gnu.org>
+
+ * defs.h (event_loop_p): Replace variable declaration with macro,
+ always 1.
+ * main.c (captured_main): Delete options "-async" and "-noasync".
+ (event_loop_p): Delete variable.
+ * NEWS: Mention that "-async" and "-noasync" were removed.
+
2004-07-16 Andrew Cagney <cagney@gnu.org>
* remote-m32r-sdi.c: Re-indent.
*** Changes since GDB 6.1:
+* "-async" and "-noasync" options removed.
+
+Support for the broken "-noasync" option has been removed (it caused
+GDB to dump core).
+
* New ``start'' command.
This command runs the program until the begining of the main procedure.
struct cmd_list_element;
/* Should the asynchronous variant of the interpreter (using the
- event-loop) be enabled? */
-extern int event_loop_p;
+ event-loop) be enabled? */
+/* NOTE: cagney/2004-06-10: GDB changed to always uses the event-loop.
+ A follow-on cleanup is to eliminate references to
+ "event_loop_p". */
+#define event_loop_p 1
extern void (*deprecated_pre_add_symbol_hook) (const char *);
extern void (*deprecated_post_add_symbol_hook) (void);
+2004-07-16 Andrew Cagney <cagney@gnu.org>
+
+ * gdb.texinfo (Mode Options): Delete documentation on "-async" and
+ "-noasync".
+
2004-07-09 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo: Fix @kindex entries so that multiple commands that
The annotation mechanism has largely been superseeded by @sc{gdb/mi}
(@pxref{GDB/MI}).
-@item -async
-@cindex @code{--async}
-Use the asynchronous event loop for the command-line interface.
-@value{GDBN} processes all events, such as user keyboard input, via a
-special event loop. This allows @value{GDBN} to accept and process user
-commands in parallel with the debugged process being
-run@footnote{@value{GDBN} built with @sc{djgpp} tools for
-MS-DOS/MS-Windows supports this mode of operation, but the event loop is
-suspended when the debuggee runs.}, so you don't need to wait for
-control to return to @value{GDBN} before you type the next command.
-(@emph{Note:} as of version 5.1, the target side of the asynchronous
-operation is not yet in place, so @samp{-async} does not work fully
-yet.)
-@c FIXME: when the target side of the event loop is done, the above NOTE
-@c should be removed.
-
-When the standard input is connected to a terminal device, @value{GDBN}
-uses the asynchronous event loop by default, unless disabled by the
-@samp{-noasync} option.
-
-@item -noasync
-@cindex @code{--noasync}
-Disable the asynchronous event loop for the command-line interface.
-
@item --args
@cindex @code{--args}
Change interpretation of command line so that arguments following the
int display_space;
-/* Whether this is the async version or not. The async version is
- invoked on the command line with the -nw --async options. In this
- version, the usual command_loop is substituted by and event loop which
- processes UI events asynchronously. */
-int event_loop_p = 1;
-
/* The selected interpreter. This will be used as a set command
variable, so it should always be malloc'ed - since
do_setshow_command will free it. */
};
static struct option long_options[] =
{
- {"async", no_argument, &event_loop_p, 1},
- {"noasync", no_argument, &event_loop_p, 0},
#if defined(TUI)
{"tui", no_argument, 0, OPT_TUI},
#endif