Re: [Kgdb-bugreport] Announce: New kgdb design available for 2.6.24 and 2.6.25
Status: Beta
Brought to you by:
jwessel
From: Jason W. <jas...@wi...> - 2008-05-20 19:22:12
|
Somethings moved around after kgdb was merged to the mainline. These are the docs for the "full kgdb" which is in the kgdb-next tree. http://kernel.org/pub/linux/kernel/people/jwessel/kgdb/ Only a subset of kgdb exists in the 2.6.26 kernel tree, which includes the x86 architecture, the kgdb core, and kgdboc. The kgdb-next branch can be found at: http://git.kernel.org/?p=linux/kernel/git/jwessel/linux-2.6-kgdb.git;a=shortlog;h=kgdb-next Jason. Milind Dumbare wrote: > Looking great. Thanks Jason, > > Could you please recheck the The kgdb documentation link > (http://kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb/) > <http://kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb/> > I was not able to open it. > > -Miline > > > On Sat, Mar 29, 2008 at 12:22 AM, Jason Wessel > <jas...@wi... <mailto:jas...@wi...>> wrote: > > > In the past few months some significant changes and cleanups occurred > on the kgdb sources. > > Most notable changes: > - The SMP lock and entry routines were re-written > - kgdb_handle_exception() was broken down into a number > sub functions. > - The kgdb long jmp handlers have been removed > - The long jmp code was replaced with kernel_probe memory functions > - The kernel trap hooks are registered dynamically, only when > a kgdb I/O driver is configured > - kgdboc was introduced kgdb over console > * Implementation for the 8250, cpm, mpsc, and pl011 uarts available > - The kgdb8250 driver was rewritten and the add_port() functions > are gone > - There is a kgdb test suite to help validate the kgdb internals and > for aiding in the validation of new arch specific support. > - Many defects were fixed related to SMP races and other problems > - Module debugging section information is organized differently > this means the old gdbmod floating around no longer works. > > > Chunks of kgdb dropped: > - The sh architecture specific implementation was not carried forward > - The ia64 architecture specific implementation was not carried > forward > - The mips and ppc kgdb specific rs232 drivers were not carried > forward > > All of the pieces that were dropped were due to the lack of hardware > to test and design on. I can try to field questions about how to port > these pieces to the new design for those folks who have this hardware > and are interested in contributing to kgdb. I would recommend first > looking at the drivers/serial/8250_kgdb.c as an example. > > > The kgdb documentation was rewritten and available at: > http://kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb/ > > There is a tree for the 2.6.24 kernel at: > http://git.kernel.org/?p=linux/kernel/git/jwessel/linux-2.6-kgdb.git;a=shortlog;h=kgdb_2.6.24 > > There is a tree for the 2.6.25-rcX kernel at: > http://git.kernel.org/?p=linux/kernel/git/jwessel/linux-2.6-kgdb.git;a=shortlog;h=kgdb-next > > > For the 2.6.26 development cycle a subset of the kgdb changes are > being submitted for a merge, which you can find at: > http://git.kernel.org/?p=linux/kernel/git/jwessel/linux-2.6-kgdb.git;a=shortlog;h=kgdb-next > > Also it is reasonably likely that the Source Forge cvs server will > no longer be used to house the kgdb development going forward. At > this point all the current development trees live at kernel.org > <http://kernel.org>. > > Thanks, > Jason. > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Kgdb-bugreport mailing list > Kgd...@li... > <mailto:Kgd...@li...> > https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport > > > > > -- > Milind Dumbare > Sr. Systems Engg. > Linsyssoft Technologies. |