[Top][All Lists]

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

Re: [Bug-gnubg] Severe side effects of makebearoff

From: Jim Segrave
Subject: Re: [Bug-gnubg] Severe side effects of makebearoff
Date: Thu, 28 Nov 2002 09:09:18 +0100
User-agent: Mutt/

On Wed 27 Nov 2002 (22:56 +0100), Holger wrote:
> Hi,
> There is a severe problem with makebearoff under Windows that probably
> causes wrong creations of the bearoff database.
> When started it returns after about a second (depending on the computer
> speed) and unblocks the shell. In case it's used without a pipe temp.db is
> then only a few 10k small.
> But the program is still running happily in the background!
> I stumbled over this when I tried to delete the temp file. I could not,
> because of access permissions. Under Win95! So much for M$ error messages.
> Well, the file was still open and in use.
> I confirmed that makebearoff was still running with WinTop.
> This makes an automatic generation of br1.c impossible, because
> makebearoff1 just takes part of the database as input since makebearoff is
> still not done. (Maybe you're lucky if you're on a fast machine.)
> When "makebearoff -o 6 -s 7999999 > temp.bd" finished, temp.db has a size
> of 1.481.407 bytes. makebearoff1 generates from this br1.c that with UNIX
> line endings has a size of 9.630.656, with DOS line endings 9.815.896
> bytes, and 185.241 lines. Btw, it's generated with UNIX line endings, which
> shouldn't be a problem, though.
> MD5 checksums:
> 4d0442566a9df8762816a1ab58fa3ab9  temp.bd
> eebe703a816c183bd22136bbe811058b  br1.c

Your make is starting parallel processes. That's not wrong, but in
this case it can have the effect you've seen. Something like this
should fix it:

@rm -f temp.bd
makebearoff -o -s 7999999 > temp.bd && makebearoff1 -o br1.c
rm -f temp.bd

Now makebearoff has to run to completion before makebearoff1 can start.

Jim Segrave           address@hidden

reply via email to

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