Re: [naviserver-devel] scheduler thread getting stuck

2020-06-04 Thread Ibrahim Tannir
On 03-Jun-20 23:41, Andrew Piskorski wrote: Is nsproxy supposed to work correctly on Windows? I had to make extensive changes in the nsproxy code to make it work on Windows. The code is Unix-centric and makes some false assumptions w.r.t. to Windows handles v.s. unix file descriptors and

Re: [naviserver-devel] scheduler thread getting stuck

2020-06-04 Thread Gustaf Neumann
On 03.06.20 21:13, Andrew Piskorski wrote: ns_thread.test [03/Jun/2020:14:25:28][4844.13bc][-tcl-nsthread:7-] Notice: update interpreter to epoch 1, trace none, time 0.219973 secs Assertion failed: (addr != ((void *)0)), file tclobj.c, line 325 [03/Jun/2020:14:25:32][4844.1dd8][-tcl-nst

Re: [naviserver-devel] scheduler thread getting stuck

2020-06-04 Thread Andrew Piskorski
On Thu, Jun 04, 2020 at 05:26:04PM +0200, Gustaf Neumann wrote: > >Assertion failed: (addr != ((void *)0)), file tclobj.c, line 325 > Probably "Ns_ThreadSelf(&tid);" does not work under windows (get the > id of the current thread). Ns_ThreadSelf() is defined in the OS specific > part (winthrea