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>
Subject: KGTP (Linux Kernel debugger and tracer) 20120424 release(doc update)[0/3]
Date: Tue, 24 Apr 2012 13:19:00 -0000 [thread overview]
Message-ID: <4F96A849.2090108@gmail.com> (raw)
KGTP is a realtime and lightweight Linux Kernel debugger and tracer.
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 http://code.google.com/p/kgtp/wiki/HOWTO#/sys/kernel/debug/gtpframe_and_offline_debug).
And it can work with Android (See http://code.google.com/p/kgtp/wiki/HowToUseKGTPinAndroid).
Now, it supports X86-32, X86-64, MIPS and ARM.
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 20120424 release.
You can get the package for it from
http://kgtp.googlecode.com/files/kgtp_20120424.tar.bz2
or
svn co https://kgtp.googlecode.com/svn/tags/20120424
The change of this release is:
* Update "How to use /sys/kernel/debug/gtpframe_pipe" in howto.
http://code.google.com/p/kgtp/wiki/HOWTO#How_to_use_/sys/kernel/debug/gtpframe_pipe
* Add How to handle "Unsupported operator (null) (52) in expression." to howto.
http://code.google.com/p/kgtp/wiki/HOWTO#How_to_handle_"Unsupported_operator_(null)_(52)_in_expressi
* Separate actions and actions src to handle the status
that will delete some actions.
* Add $bt to collect the stack and update the stack dump in the howto to make
it more clear.
http://code.google.com/p/kgtp/wiki/HOWTO#Howto_backtrace_(stack_dump)
* Update the format of example in the HOWTO to make it more clear.
* Remove the crc check and suport QStartNoAckMode+.
* Add Chinese howto.
http://code.google.com/p/kgtp/wiki/HOWTOCN
* Update a lot of parts of howto to make it more clear.
http://code.google.com/p/kgtp/wiki/HOWTO
http://code.google.com/p/kgtp/wiki/HOWTOCN
* Add introduce of $_ret to howto.
http://code.google.com/p/kgtp/wiki/HOWTO#Collect_stack_of_current_function's_caller_with_$_ret
According to the comments of Christoph and Geoff. I make 3 patches for Linux Kernel and make it looks OK with checkpatch.pl. I will post the patches for review to linux-kernel@vger.kernel.org in separate mails.
Thanks,
Hui
reply other threads:[~2012-04-24 13:19 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=4F96A849.2090108@gmail.com \
--to=teawater@gmail.com \
--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=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).