Why don't my kprintf's show up in fwkpfv?

[Michael Crawford]

FireWireKPrintf works in general because I get lots of other messages in fwkpfv.

I was concerned that my macro might not really have been definited, so
I verified it with:

#define DBG_MSG( x ) kprintf x you lose

After I post this mail I'll try calling kprintf() directly, without the macro.

kextstat shows that my driver really does load and unload. Every
function in it has:

void com_soggywizards_smashthestate::Foo()
{
DBG_MSG(( "%s >>>>\n", __func__ ));

// ...

DBG_MSG(( "%s <<<<\n", __func__ ));

return;
}

Help me out here, I'm begging you!

-- M.
--
Mike Crawford
Portland Custom Software Development
mi...@soggywizards.com
http://soggywizards.com

One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list (Darwin-...@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/darwin-drivers/darwin-drivers-garchive-96018%40googlegroups.com

This email sent to darwin-drivers...@googlegroups.com

[Michael Crawford]

I tried calling kprintf() directly rather than via a macro, but my
messages still don't show up in fwkpfv.

If I reboot then I see oodles of messages.

kextstat shows that my driver is loaded. If I kextunload it then
kextstat correctly shows that it's _not_ loaded. Both loading and
unloading should be logged by kprintf() but they're not.

Do I need to do something to enable Firewire logging from my kernel extension?

This is very puzzling; I've done lots of Mac drivers yet I've never
seen this before.

[Michael Crawford]

Also now posted to StackOverflow:

https://stackoverflow.com/questions/51599422/why-arent-my-kprintf-messages-showing-up-in-fwkpfv-do-i-need-to-enable-somet

This is very strange.

On Mon, Jul 30, 2018 at 10:20 AM, Michael Crawford

[Michael Crawford]

Jim Guyton suggested off-list that I try calling panic() instead of kprintf().

To my great surprise, despite that my kext gets loaded my target box
does _not_ panic.

However that gives me a clue that I can work with.

[Michael Crawford]

Jim Guyton quite helpfully pointed out that for my kext not to be
called by anything suggests that the matching isn't working.

Problems with driver matching are just about _always_ caused by
erroneous Info.plists.

I Should Not Drink And Code:

My Info.plist did not have any IOKitPersonalities yet. (It's a new
project FWIW.)

Greatly Chagrined,

mike

--
Mike Crawford
Portland Custom Software Development
mi...@soggywizards.com
http://soggywizards.com

One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light