Re: [naviserver-devel] ns_log output garbled on Windows

2019-01-30 Thread Andrew Piskorski
On Tue, Jan 29, 2019 at 12:28:38PM -0500, Andrew Piskorski wrote: > Hm, Ns_ThreadId() returns type uintptr_t, so why does LogToDString() > use PRIxPTR in the first place? Shouldn't it use PRIuPTR, with a "u" > for unsigned? I think so, so I switched to that. Nope, I was confused. PRIxPTR takes

Re: [naviserver-devel] ns_log output garbled on Windows

2019-01-29 Thread Andrew Piskorski
On Tue, Jan 29, 2019 at 12:02:23AM +0100, Gustaf Neumann wrote: > In case, the name is for unknown reason not initialized, the change [1] > should help. > https://bitbucket.org/naviserver/naviserver/commits/a1a07e7f1397e71809c74ca3a4bf93649affd8b2 That didn't make any difference. > The function

Re: [naviserver-devel] ns_log output garbled on Windows

2019-01-28 Thread Gustaf Neumann
On 28.01.19 16:51, Andrew Piskorski wrote: Btw, the log output differs between Windows and Linux in other minor but suspicious ways! Linux says "Notice:" as I expect, while Windows instead says "[Notice]" for the severity. The 3rd Linux field, "[-main-]", is completely missing on Windows! Like