[Top][All Lists]

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

Re: [Bug-gnubg] Fw: new gnu bug

From: Joseph Heled
Subject: Re: [Bug-gnubg] Fw: new gnu bug
Date: Sun, 22 Jun 2003 12:38:33 +1200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202

Jim Segrave wrote:

I get a core dump under FreeBSD with a devel branch build from about a week

The interesting part of the backtrace:

#0  0x28782b58 in kill () from /usr/lib/libc.so.4
#1  0x287c40d2 in abort () from /usr/lib/libc.so.4
#2  0x287a0103 in __assert () from /usr/lib/libc.so.4
#3  0x08069397 in menOffNonCrashed (anBoard=0x678e, afInput=0xbfbfcee0)
    at eval.c:1718
#4  0x080693c5 in CalculateContactInputs (anBoard=0xbfbfd0c0,
    arInput=0xbfbfcbc0) at eval.c:1734
#5  0x0806c015 in DumpContact (anBoard=0xbfbfd0c0, szOutput=0xbfbfd1a5 "",
    bgv=VARIATION_STANDARD) at eval.c:3748
#6  0x0806c45e in DumpPosition (anBoard=0xbfbfd0c0,
    szOutput=0xbfbfd190 "Evaluator: \tCRASHED\n\n", pec=0x815a9c4,
    pci=0xbfbfd080, fOutputMWC=0, fOutputWinPC=0, fOutputInvert=0)
    at eval.c:3907
#7  0x0806045b in CommandEval (sz=0x9f45c54 "") at gnubg.c:3011

menOff is 14 in menOffNonCrashed (which is reasonable)

ClassifyPosition() has decided this is a contact position at the top of
Are you sure about that? The problem I see about dump position is that it uses DumpContact for crashed, which is no longer correct to do. I will fix that.


 but the contact evaluater doesn't like having that many men

This is not unique - for an experiment, I started a game, gnubg made a
first move. I then edited the position by removing 9 of gnubg's pieces
(chosen arbitrarily). It was then my move and I asked for an evaluation but
got a core dump.

reply via email to

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