site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Hello JanakiRam, You need to set your boot args to kmem=1: sudo nvram boot-args="kmem=1" start gdb: sudo gdb /Volumes/KernelDebugKit/mach_kernel then, in gdb target darwin-kernel attach and you are connected to your live kernel Alex Am 11.11.2007 um 08:28 schrieb JanakiRam: Hi All, Please help me to learn the new technique. Thanks in Advance. -JanakiRam. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/below%40mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... yes, it is true, but what is does is that it allows you to view the Kernels memory, no more no less. No breakpoints, etc. I'm new to leopard. I've been using 2 machine debugging technique in Tiger to resolve the errors in My kext. I heard that in Leopard , there is a sophisticated way to debug the kernel on live. Is this True ? If so , Can any one point me to the links/documents which describe Live Kernel Debugging. This email sent to below@mac.com This email sent to site_archiver@lists.apple.com