[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Tracking ATA/ATAPI ioctl() calls....
On Tue, Oct 07, 2008 at 05:05:53PM -0500, Bryce Simonds wrote:
> That has failed me. I've tried building a debug version of the kernel and
> stepping through my program using gdb, but it always dies at the ioctl()
> call; and I have no idea how I can step through the kernel.
AFAIK there's none. Ho, maybe you could set a breakpoint with ddb
(the in-kernel debugger) on the ioctl routine in the kernel (e.g. cdioctl() if
you're using the cd device) and step from here.
But adding printfs is probably easier.
> I found that there was an ATADEBUG define that I put into the Makefile of a
> GENERIC kernel build, but this doesn't seem to have given me any additional
> insight into the problem. =/
You then need to set the wdcdebug_atapi_mask, wdcdebug_mask, etc, variable
to some non-0 values (read sys/dev/scsipi/atapi_wdc.c, sys/dev/ata/* and
sys/dev/ic/wdc* for details). It can be very verbose ...
Manuel Bouyer, LIP6, Universite Paris VI.
NetBSD: 26 ans d'experience feront toujours la difference
Main Index |
Thread Index |