gdb_stdtargin is only used in a single place; and, strangely, does not
follow the current UI. This patch removes the global and changes the
one user to use gdb_stdin instead.
Approved-By: Andrew Burgess <aburgess@redhat.com>
the possibly relocated path to python's lib directory. */
std::string python_libdir;
-/* Target IO streams. */
-struct ui_file *gdb_stdtargin;
-
/* True if --batch or --batch-silent was seen. */
int batch_flag = 0;
gdb_internal_backtrace_init_str ();
current_ui = main_ui;
- gdb_stdtargin = gdb_stdin;
-
/* Put a CLI based uiout in place early. If the early initialization
files trigger any I/O then it isn't hard to reach parts of GDB that
assume current_uiout is not nullptr. Maybe we should just install the
limit this read to something smaller than that - by a
safe margin, in case the limit depends on system
resources or version. */
- ret = gdb_stdtargin->read ((char *) buffer, 16383);
+ ret = gdb_stdin->read ((char *) buffer, 16383);
if (ret > 0 && (size_t)ret > length)
{
remaining_buf = (char *) xmalloc (ret - length);
/* Target output. */
#define gdb_stdtarg (*current_ui_gdb_stdtarg_ptr ())
-/* Truly global ui_file streams. These are all defined in main.c. */
-
-extern struct ui_file *gdb_stdtargin;
-
/* Set the screen dimensions to WIDTH and HEIGHT. */
extern void set_screen_width_and_height (int width, int height);