[kgtp] r1666 committed - Fix a wiki link issue
- From: kgtp@xxxxxxxxxxxxxx
- To: kgtp@xxxxxxxxxxxxx
- Date: Tue, 13 Aug 2013 00:15:01 +0000
Revision: 1666
Author: teawater
Date: Mon Aug 12 17:14:50 2013
Log: Fix a wiki link issue
http://code.google.com/p/kgtp/source/detail?r=1666
Modified:
/wiki/HOWTO.wiki
=======================================
--- /wiki/HOWTO.wiki Mon Aug 12 00:36:42 2013
+++ /wiki/HOWTO.wiki Mon Aug 12 17:14:50 2013
@@ -23,7 +23,7 @@
This table is for the people that have experience using GDB debug normal
program. It will help you understand and remember the function of KGTP.
|| *Function* || *GDB debug normal program* || *GDB control KGTP debug
Linux kernel* ||
|| Preparatory work || Have a GDB installed in your system.<br>Program
built with "-g". || KGTP need GDB 7.6 or newer version because it use some
new functions of GDB. If your system doesn't supply it，you can get new
version GDB in [http://code.google.com/p/gdbt/] and you can get an
introduce about howto built new GDB step by step in there.<br>You alse need
do some preparatory work with Linux kernel and KGTP. Please goto
[HOWTO#Preparatory_work_before_use_KGTP] get howto do it. ||
-|| Attach || Use command "gdb -p pid" or GDB command "attach pid" can
attach a program that running in the system. || Need insmod gtp.ko first,
see [#Exec_it].<br>Then let GDB connect to KGTP, see
[#Make_GDB_connect_to_gtp].<br>Please *note* that after GDB connect to
KGTP, Linux kernel will not stop. ||
+|| Attach || Use command "gdb -p pid" or GDB command "attach pid" can
attach a program that running in the system. || Need insmod gtp.ko first,
see [HOWTO#How_to_let_GDB_connect_to_KGTP].<br>Then let GDB connect to
KGTP, see [#Make_GDB_connect_to_gtp].<br>Please *note* that after GDB
connect to KGTP, Linux kernel will not stop. ||
|| Breakpoints || GDB command "b place_will_stop", let program execute
after this command. Then programe will stop in the place that setup a
breakpoint. || KGTP doesn't support breakpoints but it support
tracepoints. Tracepoints can be considered as a special kind of
breakpoints. It can be setup in some place of Linux kernel and define some
commands that you want to do in its actions. When tracepoints start, they
will execute these commands when Linux kernel execute to these place. When
tracepoint stop, you can use some GDB commands parse the data that get by
tracepoints like what you do when program stop by breakpoints.
*Difference* is breakpoints will stop the program But the tracepoints of
KGTP not. Please goto [#GDB_tracepoint] get howto use it. ||
|| Memory read || After GDB stop the program(maybe doesn't need), it can
read memory of program with GDB command "print", "x" and so on. || You can
set special actions to collect memory to traceframe in tracepoints, and get
the its value when tracepoint stop.[#collect_expr1,_expr2,_...]
[#Use_tfind_select_the_entry_inside_the_trace_frame_info] <br>Or you can
read memory directly when Linux kernel or program is
running.[#Direct_access_the_current_value_in_normal_mode] ||
|| Step and continue || GDB can continue program execution with
command "continue" and stop it with CTRL-C. || KGTP never stop the Linux
kernel. But tracepoint can be start and
stop.[#Start_and_stop_the_tracepoint] <br> Or use while-stepping tracepoint
record Linux kernel with some times single step and Let KGTP switch to
replay mode. Then it support execution commands (continue, step) and
reverse-execute commands (reverse-continue, reverse-step).
[#Use_while-stepping_let_Linux_kernel_do_single_step] ||
@@ -291,7 +291,7 @@
}}}
== Install and uninstall KGTP ==
-KGTP don't need to be install because it can insmod directly inside its
directory (See [HOWTO#Exec_it]). But if you need, you can install it to
your system.<br>
+KGTP don't need to be install because it can insmod directly inside its
directory (See [HOWTO#How_to_let_GDB_connect_to_KGTP]). But if you need,
you can install it to your system.<br>
Install:
{{{
cd kgtp/
@@ -341,7 +341,7 @@
sudo insmod gtp.ko
}}}
=== Handle the issue that cannot find "/sys/kernel/debug/gtp" ===
-If you got this issue, please make sure "Debug Filesystem" is opened in
your kernel config first.
[HOWTO#If_your_system_use_the_Linux_kernel_that_is_built_by_yourself]<br>
+If you got this issue, please make sure "Debug Filesystem" is opened in
your kernel config first. Please goto
[HOWTO#If_your_system_use_the_Linux_kernel_that_is_built_by_yourself] see
how to open it.<br>
If it is opened, please use following command mount sysfs.
{{{
@@ -392,7 +392,7 @@
adb shell insmod /gtp.ko
}}}
=== Handle the issue that cannot find "/sys/kernel/debug/gtp" ===
-If you got this issue, please make sure "Debug Filesystem" is opened in
your kernel config first.
[If_your_system_use_the_Linux_kernel_that_is_built_by_yourself]<br>
+If you got this issue, please make sure "Debug Filesystem" is opened in
your kernel config first. Please goto
[#If_use_with_Linux_kernel_of_Android] see howto open it.<br>
If it is opened, please use following command mount sysfs.
{{{
@@ -1905,7 +1905,7 @@
=== How to use ===
- * insmod KGTP module according to [HOWTO#Exec_it].
+ * insmod KGTP module according to [HOWTO#How_to_let_GDB_connect_to_KGTP].
* insmod plugin_example.ko
* Use GDB connect to KGTP and use it.
* Disconnect GDB. If option in
[HOWTO#Do_not_stop_tracepoint_when_the_GDB_disconnects] set to on, set it
to off.
Other related posts:
- » [kgtp] r1666 committed - Fix a wiki link issue - kgtp
