From b4f61fb6f52f4af1a3c4b7549fde6c9faeee4405 Mon Sep 17 00:00:00 2001 From: Brian Vincent Date: Thu, 24 Feb 2005 10:09:30 +0000 Subject: [PATCH] Clean up references to threading in Developer's Guide. --- documentation/winedev-kernel.sgml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/documentation/winedev-kernel.sgml b/documentation/winedev-kernel.sgml index ac4eb950e75..850201d45da 100644 --- a/documentation/winedev-kernel.sgml +++ b/documentation/winedev-kernel.sgml @@ -448,8 +448,7 @@ if (res != ERROR_SUCCESS) return res; in turn implies that any code which could possibly block (for instance by using a critical section) needs it. The TEB also holds the SEH exception handler chain as the - first element, so if when disassembling you see code like - this: + first element, so if disassembling you see code like this: movl %esp, %fs:0 @@ -690,7 +689,7 @@ if (res != ERROR_SUCCESS) return res; The actual wine binary that the user runs does not do very much, in fact it is only responsible for checking the threading model in use (NPTL vs LinuxThreads) and then invoking - a new binary which performs the next stage in the startup sequence. See the threading chapter + a new binary which performs the next stage in the startup sequence. See the beginning of this chapter for more information on this check and why it's necessary. You can find this code in loader/glibc.c. The result of this check is an exec of either wine-pthread or wine-kthread, potentially (on Linux) via @@ -773,7 +772,7 @@ if (res != ERROR_SUCCESS) return res; This function is responsible for initializing the primary Win32 environment. In thread_init(), it sets up the TEB, the wineserver connection for the main thread and the process heap. See - the threading chapter for more information on this. + the beginning of this chapter for more information on this. -- 2.11.4.GIT