diff options
| author | Christopher Faylor <me@cgf.cx> | 2002-08-04 03:34:01 +0400 |
|---|---|---|
| committer | Christopher Faylor <me@cgf.cx> | 2002-08-04 03:34:01 +0400 |
| commit | 2389d0af46a79878faaf4b6003e81854b327c7f9 (patch) | |
| tree | 8ec8c8593213f22481c2dc6a79013dbd65ead64d /winsup | |
| parent | eb7368d4ac3a6a0dc9be9a5d4718423ab204992e (diff) | |
update
Diffstat (limited to 'winsup')
| -rw-r--r-- | winsup/cygwin/how-signals-work.txt | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/winsup/cygwin/how-signals-work.txt b/winsup/cygwin/how-signals-work.txt index 7ab85db8b..3b36badc8 100644 --- a/winsup/cygwin/how-signals-work.txt +++ b/winsup/cygwin/how-signals-work.txt @@ -77,7 +77,11 @@ function that is known to block (such as _read()), usually by calling sets up information about the current stack frame of an executing cygwin process. Any function which uses 'sigframe thisframe' should be signal aware. It should detect when a signal has arrived and return -immediately. +immediately. This method is also used throughout the DLL to ensure +accurate frame info for the executing function. So, you'll see it +sprinkled liberally throughout the DLL, usually at places where +empirical tests have indicated problems finding this address via the +brute force method stack walking method employed in setup_handler. So, if mainframe is active, that means that we have good information about the state of the main thread. Cygwin uses the stack frame info |