Re: How to debug deadlocks in KEXT?
Re: How to debug deadlocks in KEXT?
- Subject: Re: How to debug deadlocks in KEXT?
- From: Joel Reymont <email@hidden>
- Date: Thu, 26 May 2011 22:17:45 +0200
On May 26, 2011, at 9:54 PM, Anatol Pomozov wrote:
> What I want is to setup breakpoints in some
> functions and see variables/parameters.
Worked fine for me last time I tried.
> Another question that is related to the article: how to debug KEXT on
> a single machine? Is it possible to debug deadlocks locally?
You cannot debug a kext on a local machine. Not unless you call debugging
the adding of copious logging to the driver and analyzing of this output.
--------------------------------------------------------------------------
- for hire: mac osx device driver ninja, kernel extensions and usb drivers
---------------------+------------+---------------------------------------
http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont
---------------------+------------+---------------------------------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden