Alain wrote:
dr2=22 = B19 in _both_ cases !!
which has no link with the semeais (in near J4 or T3), and is hopefully the
wrong color which cause the crash.
So it seems the bug is much earlier, in the definition of
DRAGON2(dr).semeai_defense_target
Yes, that's the purpose of the
Le Mercredi 11 Janvier 2006 23:16, alain Baeckeroot a écrit :
In test_owl_attack_move (owl.c : 4942) i have in both cases wrong dr2
int dr2 = DRAGON2(dr).semeai_defense_target;
dr2=22 = B19 in _both_ cases !!
in both cases, B19 is the first stone/dragon on the board
= i suspected
Alain wrote:
in both cases, B19 is the first stone/dragon on the board
= i suspected loop boundary problem
In engine/semeai.c : 47
#define MAX_DRAGONS 100
instead of 50 fixes the problem:
we have in one case 51 dragons, and in the other 53
The loops are fine, due to this
a not very important thing.
The mails take nearly 5 hours to arrive here, so i get it much later
than my next post :(
i dont know if it is done on purpose, but i would find it more pleasant
to get mails lets says in half an our.
We can't do anything about the slowness of the mailing
4 matches
Mail list logo
