Re: [naviserver-devel] scheduler thread getting stuck

2020-06-08 Thread Gustaf Neumann
On 04.06.20 17:26, Gustaf Neumann wrote: This sounds indeed related with the original problem. The test registers a repeating proc (interval 1s), but within in the time-range of 2.5s, it is executed only once. ... maybe i get on the weekend some access to a win environent. i could use a window

Re: [naviserver-devel] scheduler thread getting stuck

2020-06-08 Thread Andrew Piskorski
On Mon, Jun 08, 2020 at 12:04:59PM +0200, Gustaf Neumann wrote: > So, i have modified the code to use "time_t" for the "sec" member, > ... and many of the warnings disappeared. That's a big improvement, thank you, Gustaf! The 22 regression tests below used to fail, but now pass! No change to th

Re: [naviserver-devel] scheduler thread getting stuck

2020-06-08 Thread Gustaf Neumann
On 08.06.20 16:32, Andrew Piskorski wrote: On Mon, Jun 08, 2020 at 12:04:59PM +0200, Gustaf Neumann wrote: So, i have modified the code to use "time_t" for the "sec" member, ... and many of the warnings disappeared. That's a big improvement, thank you, Gustaf! The 22 regression tests below use

Re: [naviserver-devel] scheduler thread getting stuck

2020-06-08 Thread Andrew Piskorski
On Windows there are still a few compiler warnings that look a little suspicious (below), but I don't see any good way to fix these. cl /W3 /nologo /c /EHsc /MDd /Od /Zi /RTC1 /I "..\include" /I "C:\P\OpenSSL-Win64\include" /I "C:\P\Tcl-64-8.6\include" /D "_WINDOWS" /D "TCL_THREADS=1" /D "FD_

Re: [naviserver-devel] scheduler thread getting stuck

2020-06-08 Thread Andrew Piskorski
On Mon, Jun 08, 2020 at 05:46:54PM +0200, Gustaf Neumann wrote: > >Assertion failed: tid != NULL, file tclthread.c, line 238 > You might check whether "ns_thread handle" > in a classical setup (e.g. in a ds/shell) thows the same exception. Good idea. I started up NaviServer with the same tes

Re: [naviserver-devel] scheduler thread getting stuck

2020-06-08 Thread Gustaf Neumann
On 08.06.20 19:39, Andrew Piskorski wrote: On Windows there are still a few compiler warnings that look a little suspicious (below), but I don't see any good way to fix these. it is not hard to silence these cases (at least one of these appeared multiple times on stackoverflow), but these are