From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter De Schrijver Message-Id: <199812231137.MAA12554@medelec.uia.ac.be> Subject: Re: ADB spy tool To: bh40@calva.net (Benjamin Herrenschmidt) Date: Wed, 23 Dec 1998 12:37:08 +0100 (MET) Cc: linuxppc-dev@lists.linuxppc.org, linuxppc-user@lists.linuxppc.org, paulus@cs.anu.edu.au In-Reply-To: <19981223111412.008601@mail.mipsys.com> from "Benjamin Herrenschmidt" at Dec 23, 98 11:14:12 am Content-Type: text Sender: owner-linuxppc-dev@lists.linuxppc.org List-Id: > > > I've built a little tools for tracing ADB requests issued by MacOS. > There's a little INIT that records all ADB commands issues thru the > _ADBOp trap and an application for displaying those traces. It also > records the datas with the outgoing command. Since it's not a tail patch, > it won't display incoming datas, but you can use a tool like ADB Parser > to read the content of registers. > > With this tool, you can spy the activity of your device, see all the > commands issued by the driver to the device, etc... > > The INIT will start recording in a ring buffer as soon as it's loaded, so > if you want to to loard earlier, you may want to change it's type to > 'scri'. The ring buffer is about 32k and older traces are lost when it's > full. The application for emptying the buffer is PPC only unless you ask > for a 68k version. If you use MountX, make sure you don't use the debug I would like m68k versions of this, as I don't have a ppc running macos. thanks, Peter. [[ This message was sent via the linuxppc-dev mailing list. Replies are ]] [[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]] [[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]] [[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]