diff options
author | Jason Molenda <jmolenda@apple.com> | 1999-12-14 01:06:04 +0000 |
---|---|---|
committer | Jason Molenda <jmolenda@apple.com> | 1999-12-14 01:06:04 +0000 |
commit | c4093a6ab3c9ba5f830ca18d91d8b4db5b1d28ee (patch) | |
tree | 273969a6c8a28b0f0128edd803506abf025371b1 /gdb/target.h | |
parent | a3a8c91d411abe91720a2ac92b8140e1bdb41282 (diff) | |
download | ppe42-binutils-c4093a6ab3c9ba5f830ca18d91d8b4db5b1d28ee.tar.gz ppe42-binutils-c4093a6ab3c9ba5f830ca18d91d8b4db5b1d28ee.zip |
import gdb-1999-12-13 snapshot
Diffstat (limited to 'gdb/target.h')
-rw-r--r-- | gdb/target.h | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/gdb/target.h b/gdb/target.h index 73b0739189..4115eeeafd 100644 --- a/gdb/target.h +++ b/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 |