On Mon, Nov 17, 2014 at 10:36:48AM +0100, Gustaf Neumann wrote:
> The problem is not a argument-passing or memory problem,
> but seems to be a linking problem. When a file is opened in a
> module (here nslog) only this module can write successfully
> to this file. Under Windows other dlls can't wr
Hi Ibrahim,
that's a very good hint: AFIKT, all the modules used already
the
same /M* options. However, i've changed the runtime library
option from /MT* to MD* (multi-threaded version) and a quick
test (fildes to windows handle conversion) indicates that
the strange behavior is gone. Nevertheles
Hi Gustaf,
Just a hint: it is absolutely essential that all the modules on
Windows be compiled with the same model. I use -MD or -MDd.
Otherwise, each of the modules compiled with a different model
will have it's own global variables, environment and memory
segment and the two modules will no
Dear Andrew and all,
Over the weekend, I invested some more time into the windows
port and got a better understanding of the logging issue (a write()
operation succeeds inside nslog.c, but the identically operations
inside driver.c does not work; "not work" means, that the write
operation succeed
November 2014 14:00
To: [email protected]
Subject: Re: [naviserver-devel] more logging problems on Windows
On Thu, Nov 06, 2014 at 03:03:18PM +0100, Gustaf Neumann wrote:
> The seemingly same write() operation, which refuses to write to the
> access.log in driver.c work
On Thu, Nov 06, 2014 at 03:03:18PM +0100, Gustaf Neumann wrote:
> The seemingly same write() operation, which refuses to write to
> the access.log in driver.c works fine when called directly
> in nslog.c.
> https://bitbucket.org/naviserver/naviserver/commits/4cb76f20a8464fde98ac3147c6184a90442a2
Dear Andrew,
i've looked a little into "problem one", which looks very
weird to me.
The seemingly same write() operation, which refuses to write to
the access.log in driver.c works fine when called directly
in nslog.c.
My first suspicion was that write() does not work with size_t
in Windows (th
On Sun, Nov 02, 2014 at 10:27:21PM -0500, Andrew Piskorski wrote:
> Two, calling ns_logroll crashed Naviserver with this error:
>
> Debug Assertion Failed!
> f:\dd\vctools\crt_bld\self_x86\crt\src\write.c
> Line: 68
> Expression: (_osfile(fh) & FOPEN)
Once the nsd debug symbols were wo
On Windows, I see two additional problems with logging:
One, the access log file is opened and seems to get rolled/renamed
properly, but it is always empty, zero bytes! No content ever seems
to make it into the access log file.
Two, calling ns_logroll crashed Naviserver with this error:
Debug
