public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: linux-kernel@vger.kernel.org,
	"gdb@sourceware.org" <gdb@sourceware.org>,
		kgtp <kgtp@freelists.org>
Cc: 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>,
	Geoff Levand <geoff@infradead.org>,
		Steven Rostedt <rostedt@goodmis.org>,
	Randy Dunlap <rdunlap@xenotime.net>,
		Geunsik Lim <leemgs1@gmail.com>,
	Andi Kleen <andi@firstfloor.org>, Tao Ma <taoma.tm@gmail.com>
Subject: KGTP (Linux Kernel debugger and tracer) 20120605 release(user task memory access and user task stack dump available now)
Date: Tue, 05 Jun 2012 09:14:00 -0000	[thread overview]
Message-ID: <CANFwon17XNVcsSZsHmGtYnXtPuoGcNZgHtDUmZCvArVy8unkog@mail.gmail.com> (raw)

KGTP is a realtime and lightweight Linux debugger and tracer.
To use it, you don't need patch or rebuild the Linux kernel. Just
build KGTP module and insmod it is OK.

It makes Linux Kernel supply a GDB remote debug interface. Then GDB in
current machine or remote machine can debug and trace Linux through
GDB tracepoint and some other functions without stopping 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 using
offline debug (See
HOWTO#/sys/kernel/debug/gtpframe_and_offline_debug).
KGTP supports X86-32, X86-64, MIPS and ARM.
KGTP is tested on Linux kernel 2.6.18 to upstream.
And it can work with Android (See
http://code.google.com/p/kgtp/wiki/HowToUseKGTPinAndroid).

Please go to http://code.google.com/p/kgtp/wiki/HOWTO or
http://code.google.com/p/kgtp/wiki/HOWTO (Chinese) to get more info
about howto use KGTP.

Now, KGTP 20120605 release.
You can get the package for it from
http://kgtp.googlecode.com/files/kgtp_20120605.tar.bz2
or
svn co https://kgtp.googlecode.com/svn/tags/20120605

The main change of this release is:
Add new function "Read memory of user space program directly".
And use this function will not interrupt this task.
Please goto http://code.google.com/p/kgtp/wiki/HOWTO#Read_memory_of_user_space_program_directly
to get more info about it.

Add new function "collect stack (for backtrace) of user space program
in tracepoint".
With this function, you can get the stack dump of an user task from
user space to Kernel space.
Please goto http://code.google.com/p/kgtp/wiki/HOWTO#collect_stack_(for_backtrace)_of_user_space_program_in_tracepoin
to get more info about it.

Please goto http://code.google.com/p/kgtp/wiki/UPDATE get more info
about this release.

According to the comments of Christoph, Geoff and Andi.  I make lite
patch for review.  Please goto https://lkml.org/lkml/2012/5/9/90 to
see it.

Thanks,
Hui

                 reply	other threads:[~2012-06-05  9:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CANFwon17XNVcsSZsHmGtYnXtPuoGcNZgHtDUmZCvArVy8unkog@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=colyli@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=geoff@infradead.org \
    --cc=hch@infradead.org \
    --cc=kgtp@freelists.org \
    --cc=leemgs1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=mqyoung@gmail.com \
    --cc=rdunlap@xenotime.net \
    --cc=rostedt@goodmis.org \
    --cc=taoma.tm@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).