The debug seems more stable.
This is not really reproductible
Topic: Pollard's kangaroo ECDLP solver - page 127. (Read 58667 times)
Yes I reproduced the issue with 3 clients on a local network but only with the release.
The debug seems more stable.
This is not really reproductible
The debug seems more stable.
This is not really reproductible
Yes it looks like ok.
My server is still running on windows 10...
What happen if you connect a server with a fresh work file to all the running clients ? Does it stop ?
Server quit without error only if have some connections(especially not from local network)My server is still running on windows 10...
What happen if you connect a server with a fresh work file to all the running clients ? Does it stop ?
For me server without clients can work for a very long time. Problems appear when several clients are connected.
Yes it looks like ok.
My server is still running on windows 10...
What happen if you connect a server with a fresh work file to all the running clients ? Does it stop ?
My server is still running on windows 10...
What happen if you connect a server with a fresh work file to all the running clients ? Does it stop ?
I was forced to do as colleagues advised, i.e. change the save file to go any further. At the moment I wanted to check myself how it works in practice and combined the old progress file with a copy of the current one ... And here's what I saw:
Can you confirm that everything is working from the screenshots below? I wouldn't want to continue without it if it were otherwise ...
Below - winfo for each file separately (old, new, and connected dump):
OLD
NEW:
MERGED:
Can you confirm that everything is working from the screenshots below? I wouldn't want to continue without it if it were otherwise ...
Below - winfo for each file separately (old, new, and connected dump):
OLD
NEW:
MERGED:
In my Windows 10 not.
At first, the problem occurred for up to 1.5 hours. Over time, this intensified. Now I'm not able to finish # 110 because the server can restart every 2 minutes even
At first, the problem occurred for up to 1.5 hours. Over time, this intensified. Now I'm not able to finish # 110 because the server can restart every 2 minutes even
pfff... I have a server running since 30min in the debugger without problem...
No change ... Exits without a message after 44 seconds
I uploaded a new dbg release
May be a conflict between winsock.h and winsock2.h
May be a conflict between winsock.h and winsock2.h
Exactly. And as I mentioned - on Linux I have four clients on the test and for several hours without problems.
So this is not a crash but an unexpected exit ?!?
I'm investigating....
Exactly. And as I mentioned - on Linux I have four clients on the test and for several hours without problems.
So this is not a crash but an unexpected exit ?!?
I'm investigating....
Someone to add opencl support ?
So same behavior with the dbg exe and exit without a popup ?
Exactly. And as I mentioned - on Linux I have four clients on the test and for several hours without problems.
So same behavior with the dbg exe and exit without a popup ?
I did a test on linux and the problem doesn't occur there.
The effect of working on Windows with the new dbg from a moment ago:
The effect of working on Windows with the new dbg from a moment ago:
I uploaded a new dbg exe
OKAY... I kill only one to test
Do not kill clients
Ok thanks
no it is not compiled for more than 50 clients
i redo it
no it is not compiled for more than 50 clients
i redo it
OKAY. I have something...
I have disabled the client from this previous IP ... it's the same message about another machine
Second try:
I have disabled the client from this previous IP ... it's the same message about another machine
Second try:
Do you have it compiled for over 50 clients? After running for 5 minutes, nothing happens, then flies for 10 seconds and ends on the command line to close "Press any key to continue ...."
OK ... however it works ... End .bat "pause" caused what I described above: - / IP of one of the machines appeared earlier with information that it sends incorrect data.
OK ... however it works ... End .bat "pause" caused what I described above: - / IP of one of the machines appeared earlier with information that it sends incorrect data.
Jump to: