Jumbo 0.6.62 is out

[Sven]

Smaller, faster, stronger, now including the CygWin DLLs inside the archive with the binaries. On request of Guenther I also added binaries for older 64-bit CPUs.

http://www.schuelebln.de/chess/jumbo

Currently there are no 32-bit binaries available (does anyone need them?).

[Graham Banks]

Thanks, Sven.

[Sergio Martinez]

Thank you very much

[Gabor Szots]

Sven, when I uncomment either of the hash size lines the engine (new bb compine) crashes from the command line.

[joechess]

Geetting a stackdump error in both version on my windows 7 amd computer

Exception: STATUS_ILLEGAL_INSTRUCTION at rip=0010043C3F5
rax=00000000FFFFB038 rbx=0000000000000000 rcx=00000000000063D8
rdx=000000060001803F rsi=000000018024D760 rdi=0000000000000000
r8 =0000000000000000 r9 =0000000000000000 r10=00000000FFFFA9F0
r11=0000000000000000 r12=00000000FFFFCBF0 r13=0000000000000001
r14=00000000FFFFCBD0 r15=00000001802193F0
rbp=0000000000000000 rsp=00000000FFFFAB30
program=C:\ENGINE\Jumbo-0.6.62\jumbo64-0.6.62.exe, pid 744, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
00000000000 0010043C3F5 (00000000020, FF0700010302FF00, 00180047B51, 000FFFFCE00)
000FFFFCCB0 00180047BC2 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000 00180045863 (00000000000, 00000000000, 00000000000, 00000000000)
000FFFFFFF0 00180045914 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace

[Sven]

@joechess: Does your PC support SSE4.2 instructions or not? On older 64-bit hardware that does not support SSE4.2, please use this binary:

jumbo64-0.6.62-bb-sse41.exe

@Gabor: How does the crash look like? And does this only happen after changing the ini file as you described? Or also without doing so? In the latter case, please check my comment above.

A general word on the "ini file" (jumbo.ini): Jumbo does not actually require it, and in general there is no need to deal with it (you could even remove it) since options can be configured through the GUI. But since Graham once had trouble with some configuration options (I think it was the EGTB path) I created that "ini file" feature.

[joechess]

@joechess: Does your PC support SSE4.2 instructions or not? On older 64-bit hardware that does not support SSE4.2, please use this binary:

jumbo64-0.6.62-bb-sse41.exe

both the see41.exe's don’t work for me either, they load up to 267mb(can’t remember exact number now)looking like they are going to work, then just go to 0mb and die not making any moves at all.
previous version binaries work fine for me.

[Gabor Szots]

@Gabor: How does the crash look like? And does this only happen after changing the ini file as you described? Or also without doing so? In the latter case, please check my comment above.

This is the stackdump after uncommenting the ttHashSizeMB = 256 line:

Exception: STATUS_ACCESS_VIOLATION at rip=001004376D9
rax=00000003C8EDFF60 rbx=0000000001000000 rcx=0000000600018040
rdx=0000000000000000 rsi=0000000000000000 rdi=00000003C8EDFF60
r8 =00000000FFFF9ACC r9 =000000018013F700 r10=0000000100000000
r11=00000003C8E81D82 r12=0000000000000001 r13=00000000FFFFCC10
r14=00000000FFFF9C83 r15=00000000FFFF9C70
rbp=00000000FFFF9C6F rsp=00000000FFFF9B30
program=E:\Sakk\WB-engines\Jumbo\Jumbo_0.6.62-x64.exe, pid 9632, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
000FFFF9C6F 001004376D9 (00000000000, 00000000000, 00000000000, 5C6B6B61535C3A45)
000FFFF9C6F 00100444A92 (00000000020, FF0700010302FF00, 00180047B51, 000FFFFCE00)
000FFFFCCB0 00180047BC2 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000 00180045863 (00000000000, 00000000000, 00000000000, 00000000000)
000FFFFFFF0 00180045914 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace

And this is the engine output:

# will now use 1 cores (requested=1, current=0, max=4)
# new size of TT hash: 256 MB

Without touching the ini file it works OK.

[Sven]

@Gabor: How does the crash look like? And does this only happen after changing the ini file as you described? Or also without doing so? In the latter case, please check my comment above.

This is the stackdump after uncommenting the ttHashSizeMB = 256 line:

Exception: STATUS_ACCESS_VIOLATION at rip=001004376D9
rax=00000003C8EDFF60 rbx=0000000001000000 rcx=0000000600018040
rdx=0000000000000000 rsi=0000000000000000 rdi=00000003C8EDFF60
r8 =00000000FFFF9ACC r9 =000000018013F700 r10=0000000100000000
r11=00000003C8E81D82 r12=0000000000000001 r13=00000000FFFFCC10
r14=00000000FFFF9C83 r15=00000000FFFF9C70
rbp=00000000FFFF9C6F rsp=00000000FFFF9B30
program=E:\Sakk\WB-engines\Jumbo\Jumbo_0.6.62-x64.exe, pid 9632, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
000FFFF9C6F 001004376D9 (00000000000, 00000000000, 00000000000, 5C6B6B61535C3A45)
000FFFF9C6F 00100444A92 (00000000020, FF0700010302FF00, 00180047B51, 000FFFFCE00)
000FFFFCCB0 00180047BC2 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000 00180045863 (00000000000, 00000000000, 00000000000, 00000000000)
000FFFFFFF0 00180045914 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace

And this is the engine output:

# will now use 1 cores (requested=1, current=0, max=4)
# new size of TT hash: 256 MB

Without touching the ini file it works OK.

Thanks for the bug report, I could reproduce it here and found the bug. I will upload a fixed version as soon as I am done with all tests.

[Sven]

@joechess: Does your PC support SSE4.2 instructions or not? On older 64-bit hardware that does not support SSE4.2, please use this binary:

jumbo64-0.6.62-bb-sse41.exe

both the see41.exe's don’t work for me either, they load up to 267mb(can’t remember exact number now)looking like they are going to work, then just go to 0mb and die not making any moves at all.
previous version binaries work fine for me.

Could you please try to run the "jumbo64-0.6.62-bb-sse41.exe" binary from the command line, and post the output you get, together with some more information about your hardware?