bug-gnu-chess
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Problem between gnuchess 5.06 and xboard 4.2.6


From: Michael Schloh von Bennewitz
Subject: Problem between gnuchess 5.06 and xboard 4.2.6
Date: Sat, 5 Apr 2003 11:36:40 +0200
User-agent: Mutt/1.4.1i

Hello GNU Chess,

My installations of xboard and gnuchess work properly when they do
not communicate with other (playing gnuchess by command line or
xboard -ncp for example).

When I use them together, the second moves of both me and the
computer are rejected. If you look closely at my attached script
debug output (search for 'd2d4'), you will see that d2d4 is indeed
my first move. If I move 'e2e3' on my second move, xboard reports that
'd2d4' is illegal! It certainly would be an illegal move, because
there is no piece in position 'd2' after I already moved it.
However, it is not the move I chose (I did 'e2e3' instead).

You may think that this is no problem, as I can just move 'e2e3' a
second time and this time xboard will correctly recognize the move.
However, it happens as well when the computer makes its second move.
The computer has no notion of an 'incorrect' move however, so when
the error appears there is no second attempt by the computer
although it is still its turn. I am unable to move (it is not my
turn), and I have to sit and watch as the time runs out. The
computer thinks it has made its move and therefore does nothing
more.

I configured xboard with:

./configure --prefix=/opkg --sysconfdir=/opkg/etc/xboard
--localstatedir=/opkg/var/xboard --oldincludedir=/opkg/include
--x-includes=/usr/openpwin/include --x-libraries=/usr/openwin/lib
--with-x --enable-xpm --enable-sigint

I configured gnuchess with:
./configure --prefix=/opkg

My make is GNU make 3.80, and compiler is GNU gcc 3.2.2.

Please see the attached script file for details of what happens in
the interaction of gnuchess and xboard.

Regards,
Michael

P.S.:

Tim MANN suggested to me that I try configuring xboard with
--disable-sigint, and this change worked around the above problem
successfully. I am still sending you this bug report, in case you
dislike such workarounds as I do.

Attachment: bugscript.txt
Description: Text document

Attachment: pgprXx22naUG4.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]