Page 3 of 7

Re: On-line engine blitz tourney July

Posted: Sat Jul 27, 2019 9:43 pm
by Roland Chastain
WinBoard crashed again here.

Re: On-line engine blitz tourney July

Posted: Sat Jul 27, 2019 9:43 pm
by Daniel Anulliero
Too hot may be :)

Re: On-line engine blitz tourney July

Posted: Sat Jul 27, 2019 9:45 pm
by hgm
The ICS has crashed again. Because I was logged in on the server machine through ssh when it happened, I could see the error message: "stack smashing detected", plus a backtrace.

I guess this is pointless. I have no idea why it suddenly doesn't work, after many months of flawless operation. But it will take time to fix it.

So the tourney for tonight is cancelled. When I have solved the problem it will be rescheduled. Sorry about that.

Re: On-line engine blitz tourney July

Posted: Sat Jul 27, 2019 9:47 pm
by Daniel Anulliero
No problem hg
It can happen

Re: On-line engine blitz tourney July

Posted: Sat Jul 27, 2019 9:48 pm
by Sven
maybe ICS received a very long line causing a buffer overflow, which was detected by safety code introduced by gcc?

Re: On-line engine blitz tourney July

Posted: Sat Jul 27, 2019 9:49 pm
by Ronald
No problem..

It's probably been too hot the last days. :oops:

Re: On-line engine blitz tourney July

Posted: Sat Jul 27, 2019 9:50 pm
by D Sceviour
Thank you for trying. See everyone next time.

Re: On-line engine blitz tourney July

Posted: Sat Jul 27, 2019 9:52 pm
by hgm
I looked in the command log, and there is nothing suspicious there. The last logged command is a simple move, 'e3h3'.

The backtrace is all in libc library routines; Didn't tell me anything useful.

Re: On-line engine blitz tourney July

Posted: Sat Jul 27, 2019 11:05 pm
by flok
hgm wrote: Sat Jul 27, 2019 9:52 pm I looked in the command log, and there is nothing suspicious there. The last logged command is a simple move, 'e3h3'.

The backtrace is all in libc library routines; Didn't tell me anything useful.
Hmmm. I have the feeling it is Micah.
I had to enlarge a too small buffer in icsdrone to get it to work with fics.

e.g.:
Sat Jul 27 21:40:21 2019:DEBUG:engine->icsdrone: 10 +0 1 4362 Bd8 Ra6 Bf6 Rc6 h4 h3 Kg8 Rc4 Be7 Rc6 Kf8 Kd4 Bf6+ Kc4 Be7 Kd5 Kf7 Rc4 g6 Rc6 Bf6 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6\012

That's quite long :-)

Re: On-line engine blitz tourney July

Posted: Sat Jul 27, 2019 11:27 pm
by Sven
flok wrote: Sat Jul 27, 2019 11:05 pm
hgm wrote: Sat Jul 27, 2019 9:52 pm I looked in the command log, and there is nothing suspicious there. The last logged command is a simple move, 'e3h3'.

The backtrace is all in libc library routines; Didn't tell me anything useful.
Hmmm. I have the feeling it is Micah.
I had to enlarge a too small buffer in icsdrone to get it to work with fics.

e.g.:
Sat Jul 27 21:40:21 2019:DEBUG:engine->icsdrone: 10 +0 1 4362 Bd8 Ra6 Bf6 Rc6 h4 h3 Kg8 Rc4 Be7 Rc6 Kf8 Kd4 Bf6+ Kc4 Be7 Kd5 Kf7 Rc4 g6 Rc6 Bf6 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6 Kf7 Rc7+ Ke8 Rc6\012

That's quite long :-)
Maybe you want to add repetition detection ;-)