Subject: Re: How to debug my pseudo-driver
To: Steven Grunza <steven.grunza@dgms.com>
From: David Brownlee <abs@anim.dreamworks.com>
List: port-sparc
Date: 07/06/1999 12:27:14
You might be able to just put a call to Debugger() in tdopen...
David/absolute
-=- "Old Red he died, and every single landlord in the district cried" -=-
On Tue, 6 Jul 1999, Steven Grunza wrote:
> Well, I'm now to the point where my driver appears to be called at
> tdattach() and tdopen() but it isn't working correctly. The
> character device associated with /dev/td0 should return a test
> message but it doesn't.
>
> root@hw-ss1# dd if=/dev/td0 of=/tmp/t bs=1 count=20
> td: tdopen() called.
> dd: /dev/td0: Operation not permitted
> 0+0 records in
> 0+0 records out
> 0 bytes transferred in 1 secs (0 bytes/sec)
>
>
> So how do I debug this? I need the debugger to kick in when I enter
> the tdopen() routine.
>
> =======================================================
> Steven Grunza Hardware Engineer
> ------------------------------------------------------------------
> --------------------------------------------
> mailto:grunza@ulticom.com Ulticom
> voice: (856) 787 - 2759 1020 Briggs Road
> fax: (856) 866 - 2033 Mt. Laurel, NJ 08054
> cubicle: K6
> flames: /dev/null
> ------------------------------------------------------------------
> --------------------------------------------
> Unix is user friendly, it's just particular about with whom it makes
> friends.
>
>
>
>