On Thu, Oct 23, 2014 at 12:45:36PM +0200, Gustaf Neumann wrote: > By reading the code for windows "services", i see that > the corresponding thread is named "-service-". I've extended > the sanity check to include this value. if this is not > sufficient, please report, what the returned threadName is.
With your change, it still triggered the assertion. I added this code, and when run as a windows service, the logged threadName is empty string: char *threadName = Ns_ThreadGetName(); Ns_Log(Notice, "CreateConnThread: threadName is: '%s'", threadName); Does an empty string thread name indicate a problem somewhere else, or is it ok and just something special about Windows Services? The good news is, with that the assertion turned off completely, Naviserver now appears to run ok as a Windows Service, yay! -- Andrew Piskorski <a...@piskorski.com> ------------------------------------------------------------------------------ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
