From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: aplay/arecord hang at 44100 Hz Date: Tue, 11 Feb 2003 18:03:17 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <3E476DD8.7050907@uni-bonn.de> <3E49291E.7000307@uni-bonn.de> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <3E49291E.7000307@uni-bonn.de> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Josh Buhl Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Tue, 11 Feb 2003 17:47:26 +0100, Josh Buhl wrote: > > Hi, > > > i guess it's a bug of either alsa-lib or aplay, not of the driver. > > could you check at which user function the operation stops? > > > > I'll be happy to provide any debugging info I can, but I'm not exactly > sure what you mean by which user function. The error occurs for both > user functions aplay and arecord, or do you mean something else? please run aplay from gdb and break the operation to see what the program is doing there. or, a traditional debugging via printf() can be enough :) Takashi ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com