[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gnugo-devel] Crash again
From: |
Portela Fernand |
Subject: |
[gnugo-devel] Crash again |
Date: |
Sun, 13 Oct 2002 21:20:57 +0200 |
Hi,
While doing some owl-tuning, I got this somewhere in nngs3.tst (around 840)
:
***assertion failure:
reading.c:397 - !((acode != 0) && (dcode == 5 && dpos == 0)) near PASS***
The following patch solves the problem, but I haven't tried to figure out if
it makes sense or not (to me, it seems strange that more than one attack on
a
string could be stored in the persistent cache). Possibly, the problem is
somewhere else and/or "deeper" and this patch could be a bad solution.
/nando
Index: reading.c
===================================================================
RCS file: /cvsroot/gnugo/gnugo/engine/reading.c,v
retrieving revision 1.82
diff -u -r1.82 reading.c
--- reading.c 12 Oct 2002 06:47:16 -0000 1.82
+++ reading.c 13 Oct 2002 19:17:11 -0000
@@ -384,10 +384,16 @@
NULL, NULL);
di = search_persistent_reading_cache(FIND_DEFENSE, find_origin(str),
NULL, NULL);
- if (ai != -1)
- delete_persistent_reading_entry(ai);
- if (di != -1)
- delete_persistent_reading_entry(di);
+ while (ai != -1) {
+ delete_persistent_reading_entry(ai);
+ ai = search_persistent_reading_cache(ATTACK, find_origin(str),
+ NULL, NULL);
+ }
+ while (di != -1) {
+ delete_persistent_reading_entry(di);
+ di = search_persistent_reading_cache(FIND_DEFENSE, find_origin(str),
+ NULL, NULL);
+ }
acode = attack(str, &apos);
if (acode != 0)
dcode = find_defense(str, &dpos);
- [gnugo-devel] Crash again,
Portela Fernand <=