Re: [gnugo-devel] bug-report

[bump]

Are you running with experimental-owl-ext as either
a configure or runtime option?

Thank you for this bug report. Crash reports
are especially important right now because we are
trying to make sure that GNU Go 3.6, which we hope
to release soon, does not crash.

I can reproduce this crash. Here is a backtrace:

#0  add_loss_move (pos=202, target1=105, target2=185) at move_reasons.c:1004
#1  0x080815e5 in owl_reasons (color=1) at owl.c:4738
#2  0x08068908 in collect_move_reasons (color=1) at genmove.c:295
#3  0x08068c9b in do_genmove (move=0xbffff848, color=1, 
    pure_threat_value=0.400000006, allowed_moves=0x0) at genmove.c:422
#4  0x0806877e in genmove (i=0xbffff870, j=0xbffff874, color=1)
    at genmove.c:243
#5  0x080541e2 in load_and_analyze_sgf_file (gameinfo=0xbffff980)
    at play_solo.c:156
#6  0x0804a51c in main (argc=3, argv=0xbffffa24) at main.c:1092
#7  0x42017589 in __libc_start_main () from /lib/i686/libc.so.6

Daniel Bump