Dear all,
i fixed two more bugs for win64 (see [1]). The most complex
case was handling thread results (threads returning string values).
While pthread_exit() receives a pointer value (64 bit), the native
windows counter part _endthreadex() receives just a 32 bit value
(both, on win32 and win64). Since the received result is used
for setting the result-obj, the value truncation caused many
bad things to happen. This could never have worked with
win64 before.
Now all the tests of ns_thread.test should work correctly.
@Andrew: are the still show-stoppers for you,
which have to be fixed urgently?
-gn
[1]
https://bitbucket.org/naviserver/naviserver/commits/9c48894ae8e433aa4dfbe5473e9553f796ec24bd
On 08.06.20 17:46, Gustaf Neumann wrote:
No change to the other failing tests, nor to the ones that we're
currently skipping with the notWin32 constraint.
E.g., test ns_thread-2.6 still triggers this:
Assertion failed: tid != NULL, file tclthread.c, line 238
i am not surprised, since i have not changed anything around this.
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
