Re: FireWire kprintf debugging ideal for sleep

Subject: Re: FireWire kprintf debugging ideal for sleep

From: Chris Sarcone <email@hidden>

Date: Tue, 13 Feb 2007 18:13:02 -0800

Delivered-to: email@hidden

Sam --

How does FireWire kprintf differ from FireLog?

FireWireKprintf simply redirects the kprintf vector (PE_kputc) to Firewire (so it doesn't go to console or serial, it goes to firewire).

Do you still need to add a dependency on IOFireWireFamily to use it?

No. Simply call kprintf(). Remember, this adds string bloat to your kext (wired memory). Be sure to strip the kprintfs from non-debug code.

(sorry, I guess I should download it and read all about it when I get a chance) I found FireLog incredibly useful a couple of years back when I needed to get logging information out at tricky times but it would have been really cool to have been able to call it a bit more easily from any sort of kext.

Also, only having a very CPU-intensive GUI tool to read the messages was a pain, so I hacked up a command line one that was tricky to get right and still had problems occasionally when the log wrapped back to the start of the buffer.

There's a viewer included in the FireWire SDK. The only requirement is two machines, each with FireWire.

-- Chris

------------------

6 Infinite Loop

M/S 306-2MS

Cupertino CA 95014

phone: (408) 974-4033

fax: (408) 862-7577

email: email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-drivers mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

References:
	>Re: FireWire kprintf debugging ideal for sleep (From: Sam Vaughan <email@hidden>)