Re: [Kgdb-bugreport] About kgdb some questions
Status: Beta
Brought to you by:
jwessel
From: Josh Z. <jos...@gm...> - 2008-03-27 07:00:46
|
Hello Sergei, Thanks for your reply. I think I was confused with JTAG debugger. I also have some questions about it. void breakpoint(void) { ... wmb(); BREAKPOINT(); wmb(); When host gdb running "target remote udp:targetip:6443 ", kgdb will entry into kgdb_handle_exception(), my target will be stopped and any program can n't run, I can't press any key in the target. So how the kgdb implement it? I 've seen that kgdb_handle_exception(){ ... local_irq_save(flags); .. get_packet() ... local_irq_restore(flags); .. } Is it mean that I must leave local_irq_restore(flags) so that other programs can be run ? 2008/3/26, Sergei Shtylyov <ssh...@ru...>: > > Hello. > > > Josh Zhao wrote: > > > Hi everyone, I have some questions after reading kgdb patch, > > 1. Does it have porting guide? > > > See Documentation/DocBook/kgdb.tmpl (you can make pdf/ps file from > this), > I know of no other guide (besides the source itself). > There's also more complete user manual at > http://kgdb.linsyssoft.com/docu.htm... > > > > 2. Kgdb will process the data that host kgdb sent, so where is the > > > Host *gdb*. > > > protocol specification? > > Indeed where? It should be somewhere among the gdb documentation I > guess... > > > > 3.Why I haven't seen about software breakpint implemention on > > arch-kgdb(arch/blackfin/kernel),only hw breakpoint ? > > > I just looked there, and it turned out that we have a funny situation > with > Blackfin. The kgdb.c module there seems a full featured backend (even with > h/w > breakpoint support) for the new KGDB --- which hasn't been merged to the > mainline yet. The s/w breakpoints are handled in the generic way by > kernel/kgdb.c which is a part of the KGDB patchset that can be found on > http://sourceforge.net/projects/kgdb... > > > > 4. When host gdb connects to kgdb, my target board holds, I can't > press > > any key on it. So how to do by kgdb patch? > > > Load the cross-gdb on host, connect to the target as described in the > above-mentioned documetation (with gdb's 'target remote' command), and > when > this happens, just press 'c' in gdb ('continue' command) -- the target > should > resume booting. > > > Thanks!!! > > WBR, Sergei > |