I use ns_log or Ns_Log, so it should take care about it, it ends up in
Ns_DStringPrintf which calls vsnprintf.
Is it correct in x64 to pass *va_list?
Ns_VALog(Ns_LogSeverity severity, CONST char *fmt, va_list *vaPtr)
Gustaf Neumann wrote:
> be sure to terminate va_* argument lists with NULL (o
be sure to terminate va_* argument lists with NULL (or to be on the safe
side
with (char*)NULL) and not with 0. when you have sizeof(int) !=
sizeof(char *),
the compiler will put a 32bit for 0, a comparison with a 64bit null
pointer
will fail. I am pretty sure, the vsnprintf() tries to write
In it will not hurt performance when constantly asking for config
parameter with locking i am fine with it. Can be also compile time
option for configure
Vasiljevic Zoran wrote:
> So:
>
>
>The configuration is global and read-only. Parameters may be
> retrieved at
>run-time using [cm
Hi,
This is an example when it crashes inside vsnprintf, experimenting i
found that issuing long unknown command crashes as well. In my case i
noticed that trying to log long lines does not work as well. In x32
everything works fine
db:vlad[18:01:19]#uname -a
Linux db 2.6.22-ARCH #1 SMP PREEM
So:
The configuration is global and read-only. Parameters may be
retrieved at
run-time using [cmd ns_config], although usually configuration
parameters are
used by Tcl library files at start-up.
I submitted a patch/module to RFE section since some time
already, that implements the c
