Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!math.ohio-state.edu!jussieu.fr!univ-lyon1.fr!frmug.fr.net!renux.frmug.fr.net!keltia.frmug.fr.net!not-for-mail From: roberto@keltia.frmug.fr.net (Ollivier Robert) Newsgroups: comp.os.386bsd.bugs Subject: Re: Bugs in Xboing 1.8 Date: 13 Aug 1994 12:58:20 +0200 Organization: A Happy FreeBSD 1.1.5 Usenet Site Lines: 48 Message-ID: <32i90q$b4@keltia.frmug.fr.net> References: <32g8vl$6i6@ns.mcs.kent.edu> Reply-To: roberto@hsc.fr.net (Ollivier Robert) NNTP-Posting-Host: keltia.frmug.fr.net Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In article <32g8vl$6i6@ns.mcs.kent.edu>, Bret Orsburn <borsburn@mcs.kent.edu> wrote: > I've found three significant bugs in xboing 1.8 as it appears on the 2nd > issue I'm using the 2.0 and I have the same problems. > I'm running FreeBSD 1.1. 1.1.5.1 here. > The problem goes away if xboing is compiled without locking. (I have not > tried flock locking.) We don't have lockf, it is a SYSV thing. There should be a way to incorporate fcntl-type locking though. > 2) The second problem arises when audio is enabled and one attempts to > exit the program (e.g. by typing 'Q' 'Y' from the demo screen). The > current xboing child process exits immediately, but if there is an active > audio parent process, the audio parent process often (unaccountably) gets > stuck in a write to the audio device. (FWIW, I'm using a Soundblaster > Pro) There is two way to use sound with xboing. In the 2.0, there is no FreeBSDaudio.c so I took the LINUXaudio.c (the one that doesn't fork), copied it into FreeBSDaudio.c and changed the <linux/soundcard.h> to <machine/soundcard.h> and it worked like a charm. > 3) The last problem I've looked into seems to be in the game logic: from > time to time, a level fails to end when the last block is gone. This is > essentially a fatal error, because there is no way to exit the level -- > eventually, the player runs out of balls and the game ends. > I poked around in the program a little and found that sometimes > blocksExploding > 0 > > when there are no active blocks. It seems that an invariant is being violated > somewhere. I haven't looked at the code but it is pretty irritating :-( -- Ollivier ROBERT roberto@hsc.fr.net Hervé Schauer Consultants Ollivier.Robert@keltia.frmug.fr.net PERL / MIME / PGP / 4.4BSD FreeBSD keltia 1.1.5(RELEASE) RELEASE#0 i386