[Top][All Lists]

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

Re: [Bug-gnubg] unstable gnubg

From: Øystein O Johansen
Subject: Re: [Bug-gnubg] unstable gnubg
Date: Fri, 12 Nov 2004 14:21:40 +0100

> Unfortunately I can't recreate the problem following these steps.

I can!

It's even easier if you increase the move delay. Set the move delay to 3000
and you have 3 seconds to click in the dice when there is no legal move. At
the system I'm using right here now this happens.

* I setup this position:

 GNU Backgammon  Position ID: ql7wQQDbtoEBIA
                 Match ID   : EQEAAAAAAAAA
 +12-11-10--9--8--7-------6--5--4--3--2--1-+     O: gnubg
 | O           X    |   | O  O  O  O  O  O |     0 points
 | O                |   | O  O  O  O  O  O |     On roll
 |                  |   |                  |
 |                  |   |                  |
 |                  |   |                  |
^|                  |BAR|                  |
 | X                |   |                  |
 | X                |   | X                |
 | X                |   | X                |
 | X                |   | X                |
 | X              X |   | X  X  X  X  X  O |     0 points
 +13-14-15-16-17-18------19-20-21-22-23-24-+     X: user (Cube: 2)

* I set the move delay to 3000 milliseconds so I have time to click the

* I select "Play comuter turn" in the edit menu

* GNU hits something

* I dance of course

* While my dice is still on the table (in 3 seconds), I click the dice.

* I get the player cannot move dialog, and I click ok in this dialog.

* The computer rolls and moves and.....

* then it crashes.

I can not see if there is a assertion error in play.c and I see the crash
does not appear untill after gnubg moves after my dance. So there is some
difference between this and bug 9586, but since they're so similar I guess
they are related.


The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

reply via email to

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