The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Hui Zhu <teawater@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Marc Khouzam <marc.khouzam@ericsson.com>,
	Thiago Jung Bauermann <thiago.bauermann@gmail.com>,
	Steven <mqyoung@gmail.com>,
	colyli@gmail.com, Christoph Hellwig <hch@infradead.org>,
	Jason Wessel <jason.wessel@windriver.com>
Subject: Re: KGTP (Linux Kernel debugger and tracer) 20110405 release
Date: Tue, 05 Apr 2011 19:27:38 +0200	[thread overview]
Message-ID: <1302024458.2225.1350.camel@twins> (raw)
In-Reply-To: <BANLkTin7=j8-feeJw5fqDsMd9BYrq09KbQ@mail.gmail.com>

On Tue, 2011-04-05 at 19:59 +0800, Hui Zhu wrote:
> KGTP is a realtime and lightweight Linux Kernel GDB debugger and
> tracer that use Kprobe.
> 
> It make Linux Kernel supply a GDB remote debug interface. Then GDB in
> current machine or remote machine(see "Make GDB connect to gtp") can
> debug Linux through GDB tracepoint without stop the Linux Kernel.
> And even if the board doesn't have GDB on it and doesn't have
> interface for remote debug. It can debug the Linux Kernel use offline
> debug (See "Offline debug"). 

So this leaves me wondering how this is different from the existing
KGDB, if its different why its not reusing/extending the existing
infrastructure.



  parent reply	other threads:[~2011-04-05 17:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 11:59 KGTP (Linux Kernel debugger and tracer) 20110405 release Hui Zhu
2011-04-05 14:21 ` Harry Wei
2011-04-05 17:27 ` Peter Zijlstra [this message]
2011-04-06  5:54   ` Hui Zhu
2011-04-06  8:19     ` Peter Zijlstra
2011-04-08  5:36       ` Hui Zhu
2011-04-08  6:41         ` Dongdong Deng
2011-04-08  7:58           ` Hui Zhu
2011-04-08  8:25             ` Hui Zhu
2011-04-21  2:46               ` Steven Rostedt
2011-04-21  3:27                 ` Hui Zhu
2011-04-06 13:44 ` Dominique Toupin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1302024458.2225.1350.camel@twins \
    --to=peterz@infradead.org \
    --cc=colyli@gmail.com \
    --cc=hch@infradead.org \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=mqyoung@gmail.com \
    --cc=teawater@gmail.com \
    --cc=thiago.bauermann@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox