bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] Crash during play


From: Holger
Subject: Re: [Bug-gnubg] Crash during play
Date: Fri, 29 Nov 2002 17:18:08 +0100

Hi,

now I'm with you for a couple of hours, too.

At 11:47 29.11.2002 +0100, Jim Segrave wrote:
>On Fri 29 Nov 2002 (09:41 +0000), Joern Thyssen wrote:
>> On Fri, Nov 29, 2002 at 10:36:12AM +0100, Nardy Pillards wrote
>> > > Since it crashes on race positions there might be a problem with the
new
>> > > bearoff databases (gnubg uses bearoff databases for calculating bg
>> > > chances; also multiple ply may reach bearoff database).
>> > >
>> > > Has anybody been able to reproduce the problem on un*x? Especially
>> > > interesting is Jim's BSD since the memory handling is different on
those
>> > > boxses, so any possible memory problem would be more likely to show up
>> > > there.
>> > 
>> > > J?rn
>> > 
>> > The Windows builds crash:
>> > - Race position during game play
>> 
>> Does it crash on bearoff positions?
>
>Holger posted a game which he reports crashes which is in the bearoff
>stage on one side - gnubg is bearing off, holger has just come in from
>the bar. I think the other posted crashing match was also bearing off
>on at least one side.
>
>I'm very curious if br1.c on Windows has the complete database. If the
>Windows environment has a grep which supports the -n option, then it
>would be interesting to do:
>
>address@hidden:/home/jes/gnubg% grep -n '[{}]' br1.c
>31:static unsigned char acBearoff1[] = { 
>183256:};
>183260:BearoffInitBuiltin ( void ) {
>183264:  if ( ! ( pbc = (bearoffcontext *) malloc ( sizeof (
>bearoffcontext ) ) ) ) {
>183268:  }
>183286:}
>
>This tells me that the bearoff database starts on line 31 of the file
>and ends on line 183256. Could Nardy or Holger try this and see if the
>array is the same size - the difference between the line numbers for
>the open and close braces should be the same. I'm just very puzzled by
>the reported odd behaviour when building br1.c and I'd like to be sure
>that the full database is present.

C:\HB\_Projects\gnubg>grep -n '[{}]' br1.c
31:static unsigned char acBearoff1[] = {
185208:};
185212:BearoffInitBuiltin ( void ) {
185216:  if ( ! ( pbc = (bearoffcontext *) malloc ( sizeof ( bearoffcontext
) ) ) ) {
185220:  }
185238:}

So, it's the same like with Nardy. Also the extra 0x0D that Jim mentions in
a later post.

C:\HB\_Projects\gnubg>md5sum br1.c
eebe703a816c183bd22136bbe811058b *br1.c

br1.c itself is generated with  UNIX line endings (No 0x0D, only 0x0A as
line termination).


Now I've tried it with makebearoff -o 6 -s 7999999 -f temp.bd
This looks good and gives:

C:\HB\_Projects\gnubg>grep -n '[{}]' br1.c
31:static unsigned char acBearoff1[] = {
183256:};
183260:BearoffInitBuiltin ( void ) {
183264:  if ( ! ( pbc = (bearoffcontext *) malloc ( sizeof ( bearoffcontext
) ) ) ) {
183268:  }
183286:}

static unsigned char acBearoff1[] = { 
   0x67, 0x6E, 0x75, 0x62, 0x67,
0x2D, 0x4F, 0x53, 
   0x2D, 0x30, 0x36, 0x2D, 0x31, 0x35, 0x2D, 0x31, 

0x2D, 0x31, 0x2D, 0x30, 0x78, 0x78, 0x78, 0x78, 
   0x78, 0x78, 0x78, 0x78,
0x78, 0x78, 0x78, 0x78, 
   0x78, 0x78, 0x78, 0x78, 0x78, 0x78, 0x78, 0x0A,

   0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x01, 0x00, 
   0x02, 0x00, 0x00,
0x00, 0x01, 0x01, 0x01, 0x00, 
   0x04, 0x00, 0x00, 0x00, 0x01, 0x01, 0x01,
0x00,  

C:\HB\_Projects\gnubg>md5sum br1.c
5e64b5ed090b73649ebea1fa7f97cf1c *br1.c

Just tried my two example matches where it crashed.

IT WORKS!

Regards,

        Holger




reply via email to

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