binutils-gdb/gdb/event-loop.h

116 lines
5.1 KiB
C
Raw Normal View History

1999-05-11 22:29:07 +02:00
/* Definitions used by the GDB event loop.
Copyright (C) 1999, 2000, 2007, 2008 Free Software Foundation, Inc.
1999-05-11 22:29:07 +02:00
Written by Elena Zannoni <ezannoni@cygnus.com> of Cygnus Solutions.
This file is part of GDB.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
1999-05-11 22:29:07 +02:00
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>. */
1999-05-11 22:29:07 +02:00
/* An event loop listens for events from multiple event sources. When
an event arrives, it is queued and processed by calling the
appropriate event handler. The event loop then continues to listen
for more events. An event loop completes when there are no event
sources to listen on. External event sources can be plugged into
the loop.
There are 3 main components:
- a list of file descriptors to be monitored, GDB_NOTIFIER.
- a list of events that have occurred, EVENT_QUEUE.
- a list of signal handling functions, SIGHANDLER_LIST.
GDB_NOTIFIER keeps track of the event sources. Event sources for
gdb are currently the UI and the target. Gdb communicates with the
command line user interface via the readline library and usually
communicates with remote targets via a serial port. Serial ports
are represented in GDB as file descriptors and select/poll calls.
For native targets instead, the communication consists of calls to
ptrace and waits (via signals) or calls to poll/select (via file
descriptors). In the current gdb, the code handling events related
to the target resides in the wait_for_inferior function and in
various target specific files (*-tdep.c).
EVENT_QUEUE keeps track of the events that have happened during the
last iteration of the event loop, and need to be processed. An
event is represented by a procedure to be invoked in order to
process the event. The queue is scanned head to tail. If the
event of interest is a change of state in a file descriptor, then a
call to poll or select will be made to detect it.
If the events generate signals, they are also queued by special
functions that are invoked through traditional signal handlers.
The actions to be taken is response to such events will be executed
when the SIGHANDLER_LIST is scanned, the next time through the
infinite loop.
Corollary tasks are the creation and deletion of event sources. */
typedef void *gdb_client_data;
1999-09-22 05:28:34 +02:00
struct async_signal_handler;
1999-10-06 01:13:56 +02:00
typedef void (handler_func) (int, gdb_client_data);
1999-09-22 05:28:34 +02:00
typedef void (sig_handler_func) (gdb_client_data);
typedef void (timer_handler_func) (gdb_client_data);
1999-05-11 22:29:07 +02:00
/* Where to add an event onto the event queue, by queue_event. */
typedef enum
{
/* Add at tail of queue. It will be processed in first in first
out order. */
TAIL,
/* Add at head of queue. It will be processed in last in first out
order. */
1999-07-07 22:19:36 +02:00
HEAD
1999-05-11 22:29:07 +02:00
}
queue_position;
/* Tell create_file_handler what events we are interested in.
This is used by the select version of the event loop. */
#define GDB_READABLE (1<<1)
#define GDB_WRITABLE (1<<2)
#define GDB_EXCEPTION (1<<3)
1999-06-28 18:06:02 +02:00
/* Exported functions from event-loop.c */
1999-06-14 20:08:47 +02:00
1999-09-22 05:28:34 +02:00
extern void start_event_loop (void);
extern int gdb_do_one_event (void *data);
1999-09-22 05:28:34 +02:00
extern void delete_file_handler (int fd);
1999-09-28 23:55:21 +02:00
extern void add_file_handler (int fd, handler_func * proc, gdb_client_data client_data);
extern struct async_signal_handler *
create_async_signal_handler (sig_handler_func * proc, gdb_client_data client_data);
extern void delete_async_signal_handler (struct async_signal_handler **async_handler_ptr);
extern int create_timer (int milliseconds, timer_handler_func * proc, gdb_client_data client_data);
1999-09-22 05:28:34 +02:00
extern void delete_timer (int id);
/* Call the handler from HANDLER immediately. This function
runs signal handlers when returning to the event loop would be too
slow. Do not call this directly; use gdb_call_async_signal_handler,
below, with IMMEDIATE_P == 1. */
void call_async_signal_handler (struct async_signal_handler *handler);
/* Call the handler from HANDLER the next time through the event loop.
Do not call this directly; use gdb_call_async_signal_handler,
below, with IMMEDIATE_P == 0. */
void mark_async_signal_handler (struct async_signal_handler *handler);
/* Wrapper for the body of signal handlers. Call this function from
any SIGINT handler which needs to access GDB data structures or
escape via longjmp. If IMMEDIATE_P is set, this triggers either
immediately (for POSIX platforms), or from gdb_select (for
MinGW). If IMMEDIATE_P is clear, the handler will run the next
time we return to the event loop and any current select calls
will be interrupted. */
void gdb_call_async_signal_handler (struct async_signal_handler *handler,
int immediate_p);