From alsa-devel-owner@alsa.jcu.cz  Wed Feb  3 23:11:02 1999
Received: from www.tridentmicro.com (www.tridentmicro.com [208.1.233.222])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id XAA20296
	for <Alsa-devel@alsa.jcu.cz>; Wed, 3 Feb 1999 23:09:30 +0100
From: bholder@tridentmicro.com
Received: from tridentmicro.com ([208.1.233.4] (may be forged))
          by www.tridentmicro.com (2.5 Build 2639 (Berkeley 8.8.6)/8.8.4) with SMTP
	  id OAA22158 for <Alsa-devel@alsa.jcu.cz>; Wed, 03 Feb 1999 14:13:04 GMT
Received: from ccMail by tridentmicro.com (ccMail Link to SMTP R8.31.00.5)
    id AA918079862; Wed, 03 Feb 1999 14:11:07 -0800
Message-Id: <9902039180.AA918079862@tridentmicro.com>
Date: Wed, 03 Feb 1999 15:03:40 -0800
To: <Alsa-devel@alsa.jcu.cz>
Subject: debug new driver
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

What are the procedures for debugging an ALSA driver? I have written a new
driver and have it compiled and linked. When I load the module (modprobe
snd-mysound) it reboots the PC. I am used to debugging sound drivers under
Windows using SoftICE. I have used gdb under Unix before, but am unsure how to
use it to debug something other than a user level program. Sorry if this is FAQ.
bob


