Re: [gnugo-devel] about one GNU Go 3.7.7 windows build's test case( crash )

[Jens Yllman]

Hi,

I don't know the current state of the 'build with VC++' part of GNU 
Go is at the moment. Often the development versions of GNU Go are not 
up to date. And all options are not available. One reason for this is 
that what I know there is no-one at the moment that is 'responsible' 
for the VC++ part.

That said, just looking at the 'Run-Time Check Failure #2 - Stack 
around the variable 'vpos' was corrupted.' message sounds to me that 
this is another of thoose parts where developers miss that diffrent 
platforms/compilers have diffrent settings. I could be wrong.

The reason for my answer to this is that I felt you got no respons 
from the more 'active' developers. Probably due to holidays. So I 
just felt I had to say something to keep your spirit up.

Another note, talking about two problems in same e-mail often make 
one of the problems disapear. Also, look at http://trac.gnugo.org/. 
There there is a testcase discussions page. If you want to talk about 
testcases before submitting patch.

Jens Yllman

At 02:26 2006-01-05, you wrote:
> Hi,
>     Sorry for not providing enough information in my previous post.
>
>     My platform is Windows XP.
>
>     I use "gnugo --mode gtp < testfile" to reproduce the crash.
>
>     I build gnugo with VC++ 7 in debug mode
>
>     When crashs, it prompts:
>
> Debug Error!
>
> Program: gnugo-3.7.7\interface\gnugo.exe
> Module: gnugo-3.7.7\interface\gnugo.exe
> File: gnugo-3.7.7\engine\optics.c
> Line: 1552
>
> Run-Time Check Failure #2 - Stack around the variable 'vpos' was corrupted.
>
> During my building,
>     GNU Go 3.7.7 's windows build seems broken. I manual built the 
> uncompress_fuseki.c and generated fuseki[9,13,19].c
>
> I also built 3.7.7 in my linux box and executed the test case. It 
> workd fine(produce "A4", though I think the best move should be B3).
>
> By the way, I think the move 102 is not best. It made left-bottom 
> group gains zero points. It should be A4|A3. But it's strange that 
> gnugo produce B5 at game and when I use test.sh to reproduce it, it 
> produce C6 though I use same command line to call gnugo.
>
> Best Regards!
>
>                 Cai Qiang
>
> ----- Original Message -----
> From: "alain Baeckeroot" <address@hidden>
> To: "Cai Qiang" <address@hidden>
> Sent: Wednesday, January 04, 2006 9:59 PM
> Subject: Re: [gnugo-devel] GNU Go
>
>
> i cant reproduce the crash
> Could you give more information about how you crash gnugo ?
> - which plateform
> - which command line you use ...
>
> thanks a lot
> Alain
> ......
> _______________________________________________
> gnugo-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnugo-devel