aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2020-02-12 17:05:42 -0700
committerTom Tromey <tom@tromey.com>2020-02-12 17:16:50 -0700
commitd1437c0ea6708204fcadbf2c305fcaa40df00866 (patch)
tree90aca3477c339e0a0cc5f0ea7671a19892000002
parentc273235f6c7784780b80388d8f3c3f5765417fb6 (diff)
downloadgdb-d1437c0ea6708204fcadbf2c305fcaa40df00866.zip
gdb-d1437c0ea6708204fcadbf2c305fcaa40df00866.tar.gz
gdb-d1437c0ea6708204fcadbf2c305fcaa40df00866.tar.bz2
Remove some dead code from event-loop.c
This removes some dead code from event-loop.c. This patch is from my old series to merge the gdb and gdbserver event loops; but since it is just removing dead code, it seemed simple to commit it separately. gdb/ChangeLog 2020-02-12 Tom Tromey <tom@tromey.com> * event-loop.c (event_data, gdb_event, event_handler_func): Remove.
-rw-r--r--gdb/ChangeLog5
-rw-r--r--gdb/event-loop.c33
2 files changed, 5 insertions, 33 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index f9dd0b6..62f786f 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,10 @@
2020-02-12 Tom Tromey <tom@tromey.com>
+ * event-loop.c (event_data, gdb_event, event_handler_func):
+ Remove.
+
+2020-02-12 Tom Tromey <tom@tromey.com>
+
* dwarf2/frame.c (dwarf2_frame_bfd_data): New global.
(dwarf2_frame_objfile_data): Add comment.
(find_comp_unit, set_comp_unit): New functions.
diff --git a/gdb/event-loop.c b/gdb/event-loop.c
index 62f8c20..af8f80b 100644
--- a/gdb/event-loop.c
+++ b/gdb/event-loop.c
@@ -43,39 +43,6 @@
#define GDB_WRITABLE (1<<2)
#define GDB_EXCEPTION (1<<3)
-/* Data point to pass to the event handler. */
-typedef union event_data
-{
- void *ptr;
- int integer;
-} event_data;
-
-typedef struct gdb_event gdb_event;
-typedef void (event_handler_func) (event_data);
-
-/* Event for the GDB event system. Events are queued by calling
- async_queue_event and serviced later on by gdb_do_one_event. An
- event can be, for instance, a file descriptor becoming ready to be
- read. Servicing an event simply means that the procedure PROC will
- be called. We have 2 queues, one for file handlers that we listen
- to in the event loop, and one for the file handlers+events that are
- ready. The procedure PROC associated with each event is dependant
- of the event source. In the case of monitored file descriptors, it
- is always the same (handle_file_event). Its duty is to invoke the
- handler associated with the file descriptor whose state change
- generated the event, plus doing other cleanups and such. In the
- case of async signal handlers, it is
- invoke_async_signal_handler. */
-
-typedef struct gdb_event
- {
- /* Procedure to call to service this event. */
- event_handler_func *proc;
-
- /* Data to pass to the event handler. */
- event_data data;
- } *gdb_event_p;
-
/* Information about each file descriptor we register with the event
loop. */