[Crash-utility] Re: [ANNOUNCE][RFC][PATCH] Crash-utility, tracing: enable crash to analyze tracing from core-file (make tracing can act as a flight recorder)

Peter Zijlstra wrote: With respect to kdb for the mainline, this is still largely a work in progress, but there is a prototype implementation of kdb which is hooked up to the kdb backend. There is a new prototype pushed to the kgdb development tree every couple of weeks. The prototype #4 will be pushed sometime this week. If there is a nice API to call for the trace piece, it is pretty trivial to add additional kdb commands which would allow you to print your trace buffers as needed. The unified kdb/kgdb prototype also supports calling kdb commands through gdb's "monitor" command. It is not clear if that satisfies the need that Christoph asked about, or if he had some other data analysis in mind. In no particular order, tracing, kernel probes, profiling data display, kdump, disassembly and kernel mode setting were some of the pieces that are on the wish list for integration with the kdb prototype. Kernel mode setting is presently the highest priority on the wish list for a new feature. I will gladly accept patches into the kdb prototype if people have any. :-) Jason. Prototype #3 is at: http://git.kernel.org/?p=linux/kernel/git/jwessel/linux-2.6-kgdb.git;a=sh... There had not been any further posts about the kdb -> kgdb integration outside the first because the project is still pretty young and there is a significant amount of clean up required to the original kdb code base in order bring it closer to consideration for any kind of lkml scrutiny. The nice thing about the kdb prototype is that it is almost entirely arch independent. The goal of this project is to make such that any arch that makes use of the kgdb core today, could make use of the generic kdb interface.