From alsa-devel-owner@alsa.jcu.cz  Thu Feb  4 10:31:25 1999
Received: from entry.jcu.cz (IDENT:perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id KAA02689;
	Thu, 4 Feb 1999 10:31:15 +0100
Date: Thu, 4 Feb 1999 10:31:15 +0100 (CET)
From: Jaroslav Kysela <perex@jcu.cz>
To: bholder@tridentmicro.com
cc: Alsa-devel@alsa.jcu.cz
Subject: Re: debug new driver
In-Reply-To: <9902039180.AA918079862@tridentmicro.com>
Message-ID: <Pine.LNX.3.96.990204102756.8890B-100000@entry.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

On Wed, 3 Feb 1999 bholder@tridentmicro.com wrote:

> 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.

Whole ALSA driver is debugged only with using printk outputs ;-))
Debugger gdb can be used only for read-only debugging for kernel code and
I think that you cannot set breakpoints.

My recommendation is debug your driver step by step (small pieces of
the code)..

							Jaroslav

-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic


