import gdb-1999-12-13 snapshot
This commit is contained in:
parent
a3a8c91d41
commit
c4093a6ab3
63 changed files with 1167 additions and 391 deletions
13
gdb/target.h
13
gdb/target.h
|
@ -104,7 +104,18 @@ enum target_waitkind
|
|||
/* Nothing happened, but we stopped anyway. This perhaps should be handled
|
||||
within target_wait, but I'm not sure target_wait should be resuming the
|
||||
inferior. */
|
||||
TARGET_WAITKIND_SPURIOUS
|
||||
TARGET_WAITKIND_SPURIOUS,
|
||||
|
||||
/* This is used for target async and extended-async
|
||||
only. Remote_async_wait() returns this when there is an event
|
||||
on the inferior, but the rest of the world is not interested in
|
||||
it. The inferior has not stopped, but has just sent some output
|
||||
to the console, for instance. In this case, we want to go back
|
||||
to the event loop and wait there for another event from the
|
||||
inferior, rather than being stuck in the remote_async_wait()
|
||||
function. This way the event loop is responsive to other events,
|
||||
like for instance the user typing. */
|
||||
TARGET_WAITKIND_IGNORE
|
||||
};
|
||||
|
||||
/* The numbering of these signals is chosen to match traditional unix
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue