[CF-Devel] Experimental crossfire-client-1.7.0 available for testing

[crossfire-devel at archives.real-time.com]

This bug is since release 1.7 of client
(see #crossfire channel topic: if your client freeze, disable sound).

Seems in some alsa configuration, the sound server does not initialize the sound card correctly but doesn't notice it. So the first attempt to send datas to sound device does freeze sound server. At the same time, client is sending sound commands to the sound server using a pipe. The buffer of the pipe is filling and at some time is full. When this happen, the client enters sleep mode, waiting for his datas to be sent. If you do plug gdb externally to the client using command 'gdb programfile pid' you'll notice the client is simply sleeping in a stdlib pipe writing function.

I have to apologize. I *forgot* to fix this since i found that bug. More shame on me as i wrote the buggy code (in client, not sound server). Need to configure pipe so it doesn't non blocking IO.

-----Original Message-----
From: Todd Mitchell <
     
     temitchell at sympatico.ca
     
     >
To: crossfire dev <
     
     crossfire-devel at lists.real-time.com
     
     >, 
     
     tanner at real-time.com
     
     
Date: Sun, 03 Oct 2004 13:00:25 -0400
Subject: Re: [CF-Devel] Experimental crossfire-client-1.7.0 available for testing

I was getting regular lockups with the debian gcfclient binary - it
would just lock and GDB would report nothing but the client had to be
killed.
Installed Valgrind and ran the client with that and naturally it didn't
lockup at all (at least untill I had to stop).  The only difference is I
installed the sound package (deb crossfire-client-sounds).  I will keep
on playing.  There were some errors showing in the Valgrind log but as I
say it appeared to run fine.  Maybe I'll try again wo/ sound although it
is nice to have noises again.


On Thu, 2004-09-30 at 09:40, Bob Tanner wrote:
>
     
      On Wednesday 22 September 2004 02:34 pm, Todd Mitchell wrote:
     
     >
     
      > Bob Tanner wrote:
     
     >
     
      > >UNLike the official 1.7.0 debian release ;-) sound IS active in this
     
     >
     
      > > package, but -fully- UNTESTED.
     
     >
     
      > >
     
     >
     
      > >Just wanted to get this out there for people to play with (Todd are you
     
     >
     
      > >reading this? :-P)
     
     >
     
      >
     
     >
     
      > I have been using your debian built client for a while now - it
     
     >
     
      > installed fine on my system (unstable - mostly to date) but I did notice
     
     >
     
      > it would hang after playing for a while.  I haven't had time to figure
     
     >
     
      > out if that is me or the client since I am using a *mostly* updated
     
     >
     
      > unstable system.  I'll try to capture the error with gdb if it
     
     >
     
      > persists.  I will update the client from your source and check it again
     
     >
     
      > soon (However I may be watching STARWARS with my kids over the next few
     
     >
     
      > nights).
     
     >
     
     
     >
     
      I'll build a -dbg version so the symbols stay out there to make gdb work a 
     
     >
     
      little better.
     
     >
     
     
     >
     
      As an aside, I've found the valgrind works pretty well on stripped binaries.
     
     >
     
     
     >
     
      These are the debian packages I have installed:
     
     >
     
     
     >
     
      kcachegrind
     
     >
     
      valgrind
     
     



_______________________________________________
crossfire-devel mailing list
     
     crossfire-devel at lists.real-time.com
     
     
     https://mailman.real-time.com/mailman/listinfo/crossfire-devel