You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by nd...@apache.org on 2002/12/16 00:05:27 UTC
cvs commit: httpd-2.0/docs/manual/developer filters.html thread_safety.html
nd 2002/12/15 15:05:27
Modified: docs/manual/developer filters.html thread_safety.html
Log:
fix html errors
Revision Changes Path
1.4 +1 -1 httpd-2.0/docs/manual/developer/filters.html
Index: filters.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/developer/filters.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- filters.html 14 Jun 2002 09:32:26 -0000 1.3
+++ filters.html 15 Dec 2002 23:05:27 -0000 1.4
@@ -16,7 +16,7 @@
<h1>How filters work in Apache 2.0</h1>
<p>Warning - this is a cut 'n paste job from an email:
- <022501c1c529$f63a9550$7f00000a@KOJ></p>
+ <022501c1c529$f63a9550$7f00000a@KOJ></p>
<pre>
There are three basic filter types (each of these is actually broken
1.14 +4 -2 httpd-2.0/docs/manual/developer/thread_safety.html
Index: thread_safety.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/developer/thread_safety.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- thread_safety.html 16 Aug 2002 17:58:14 -0000 1.13
+++ thread_safety.html 15 Dec 2002 23:05:27 -0000 1.14
@@ -50,9 +50,11 @@
If one thread calls a low-level function that sets errno and then another thread checks it, we
are bleeding error numbers from one thread into another. To solve this, make sure your module
or library defines _REENTRANT or is compiled with -D_REENTRANT. This will make errno a per-thread
- variable and should hopefully be transparent to the code. It does this by doing something like this:
+ variable and should hopefully be transparent to the code. It does this by doing something like this:</p>
+
<pre>#define errno (*(__errno_location()))</pre>
- which means that accessing errno will call __errno_location() which is provided by the libc. Setting
+
+ <p>which means that accessing errno will call __errno_location() which is provided by the libc. Setting
_REENTRANT also forces redefinition of some other functions to their *_r equivalents and sometimes
changes the common getc/putc macros into safer function calls. Check your libc documentation for
specifics. Instead of, or in addition to _REENTRANT the symbols that may affect this are