Re: Kernel extension debugging tool?
Re: Kernel extension debugging tool?
- Subject: Re: Kernel extension debugging tool?
- From: "Peter Sichel" <email@hidden>
- Date: Sun, 13 Nov 2005 22:18:12 -0500
On 11/12/05, Daniel Azuelos wrote:
>What's the best way, method to debug a kernel extension?
>I've a slow memory leak to locate precisely and l can't wait the many
>hours it needs to lead to a real system problem.
The classic answer is two machine debugging, but I've shied away from
the complexity of this. Another handy tool is Shark because it sees
everything regardless of where it is running.
My own preferred answer was to develop a test harness that allows me to
run most of my NKE code from an application context and then develop a
battery of test cases to exercise it.
No single approach is ideal, but the later makes it easier to do basic
unit and regression testing. Once the code is debugged in client space,
I use a combination of print statements (logging) and my own GUI to
verify operation while running in the kernel.
Kind Regards,
- Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden