From 2389d0af46a79878faaf4b6003e81854b327c7f9 Mon Sep 17 00:00:00 2001 From: Christopher Faylor Date: Sat, 3 Aug 2002 23:34:01 +0000 Subject: update --- winsup/cygwin/how-signals-work.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'winsup') 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 -- cgit v1.2.3