[docs] Dev guide threading references

Brian Vincent vinn at theshell.com
Wed Feb 23 14:21:01 CST 2005


Clean up references to threading in Developer's Guide.

-Brian


Index: winedev-kernel.sgml
===================================================================
RCS file: /home/wine/wine/documentation/winedev-kernel.sgml,v
retrieving revision 1.2
diff -u -r1.2 winedev-kernel.sgml
--- winedev-kernel.sgml	4 Nov 2004 21:06:14 -0000	1.2
+++ winedev-kernel.sgml	23 Feb 2005 20:18:45 -0000
@@ -690,7 +690,7 @@
 	<para>
 	  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
 	  <filename>loader/glibc.c</filename>. The result of this check is an exec of either
 	  wine-pthread or wine-kthread, potentially (on Linux) via
@@ -773,7 +773,7 @@
 	<para>
 	  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.
 	</para>
 
 	<para>
Index: threading.sgml
===================================================================
RCS file: /home/wine/wine/documentation/threading.sgml,v
retrieving revision 1.2
diff -u -r1.2 threading.sgml
--- threading.sgml	15 Jun 2004 18:26:52 -0000	1.2
+++ threading.sgml	23 Feb 2005 20:18:45 -0000
@@ -237,7 +237,7 @@
       The TEB is required by nearly all Win32 code run in the Wine environment, as any wineserver
       RPC will use it, which 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:
+      the first element, so if disassembling you see code like this:
     </para>
 
     <programlisting> movl %esp, %fs:0 </programlisting>



More information about the wine-patches mailing list