[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modules
Subject:    Re: [apache-modules] own module causes segmentation fault
From:       Christian Parpart <cparpart () surakware ! net>
Date:       2003-03-18 11:26:06
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 18 March 2003 8:19 am, Adrian.Florea inspired the electrons to say:
> Hi,
>
> maybe it will work if you use only sys calls like open/read/write instead
> of fprintf ... . Fucntions like fprintf use buffered I/O - you can avoid
> this using read/write sys calls.

You may be wrong as well. stdout/stderr are working line buffered, that means, 
writing to them does not cause to be shown on the screen unless a linefeed 
has been written (\n) to that stream.

Other things that cause buffer flushing are fsync() (as I said) and reading 
from stdin, if you just write "test", it's only flushed when putting a "\n" 
behind, calling fsync, or calling read from stdin... ah, and of course when 
exit gets called.

the write syscall is line buffered on stdout/stderr as well.

Greets,
Christian Parpart.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+dwJRPpa2GmDVhK0RAl9qAJ9gc32OmKvUqlk4DM7ILavBXbRFwACeLBZ+
bZzqvfGyJGPNztN2ZgZyWbE=
=JqkL
-----END PGP SIGNATURE-----


---------------------------------------------------------------------
To unsubscribe, e-mail: apache-modules-unsubscribe@covalent.net
For additional commands, e-mail: apache-modules-help@covalent.net


[prev in list] [next in list] [prev in thread] [next in thread]