From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: valgrind and alsa Date: Thu, 24 Feb 2005 21:58:43 +0100 Message-ID: References: <421D9482.3090807@cs.ubc.ca> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII In-Reply-To: <421D9482.3090807@cs.ubc.ca> Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: "Charles \"Buck\" Krasic" Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Thu, 24 Feb 2005 00:46:58 -0800, Charles "Buck" Krasic wrote: > > [1 ] > Hi, > > I'm new to alsa development. I have just implemented native alsa > support in an application I've developed (a streaming video system). > When checking my application with valgrind, valgrin generates numerous > alsa related warnings. They all seem to originate from a single > problem in my initial call to snd_pcm_writei. Basically valgrind > doesn't like that alsa is making an ioctl with unitialized data. The > following patch fixed the problem for me, it's just a one liner add the > missing initializtion. Thanks for the patch. I fixed the CVS code together with other parts calling ioctls. Takashi ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click