On Thursday, July 25, 2002, at 02:51 PM, Scott Taggart wrote: How do you get the kernel buffer to dump out to the screen? Unfortunately, the tool to read the trace buffer, decode the raw trace and generate a report is not open sourced yet. :-( Look at xnu/bsd/kern/kdebug.c for the implementation details. You can use sysctl(3) to get at that buffer and get the raw trace data .... Look at xnu/bsd/kern/kern_sysctl.c for the implementation of "KERN_DEBUG" and kdebug_ops() for "KERN_KDENABLE", "KERN_KDSETBUF", "KERN_KDREADTR", etc... --Umesh At 01:19 PM 7/25/2002, Umesh Vaishampayan wrote: On Thursday, July 25, 2002, at 10:15 AM, Heiko Panther wrote: Hi! Some functions I use in the kernel (e.g. thread_funnel_set(), sosend()) sometimes fail and I want to know more about it. I see they have KERNEL_DEBUG/kernel_debug() calls built in, but I get no output to system.log. I have a 10.1.5 debug kernel, and I set kdebug_enable=true before I call the function in question. What should I do? Thanks Heiko Panther KERNEL_DEBUG() traces do not go to the system.log. They are logged into a kernel buffer. --Umesh -- Umesh Vaishampayan Apple Computer, Inc. Mac OS X Kernel Ph: (408) 974 0229 _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.